More observations about checked vs. unchecked exceptions and why unchecked exceptions should not be called "exception". I rather suggest "explainer". Thy explain why an operation could not be performed.

https://miamao.de/blog/2026-02/23.When_is_an_Exception_an_Exception.html

#exception #uncheckedException #Java #TypeScript #Python #Rust

Junior Devs Use try-catch Everywhere. Senior Devs Use These 4 Exception Handling Patterns

Try-catch on every method? That’s not safe code — that’s a ticking time bomb. Here’s what senior devs do instead.

Medium

Terrific explanation of the inner-workings of the #CommonLisp condition system (a powerful superset of #exception handling that can do way more cool stuff, like restarts): https://www.youtube.com/watch?v=pkqQq2Hwt5o

Basically, the condition system itself is built directly in Common Lisp using facilities in the language that are available to the user: dynamic variables, closures, and non-local flow-control (tagbody/go and block/return-from). Nice syntax/structure provided by macros, of course. Fucking brilliant.

Immutable Conversations | Common Lisp

Immutable Conversations is a video series from 47 Degrees featuring casual conversations about important open source libraries with maintainers and contribut...

YouTube

Wenn du gerade erst mit dem Programmieren in Java startest, wirst du relativ schnell über einen Begriff stolpern: "Fail Fast". Klingt erstmal nach einem fancy Buzzword, steckt aber etwas sehr Handfestes dahinter: Der Code soll möglichst früh, möglichst klar und möglichst laut kaputtgehen, wenn

https://magicmarcy.de/fail-fast-statt-spaet-kaputt

#Fail #Exception #Java #Vorbedingungen #IllegalArgumentException #FailFast #Programming

Fail Fast statt spät kaputt: Sauberer Java-Code durch klare Vorbedingungen | magicmarcy.de

Wenn du gerade erst mit dem Programmieren in Java startest, wirst du relativ schnell über einen Begriff stolpern: "Fail Fast". Klingt erstmal nach einem fancy Buzzword, steckt aber etwas sehr Handfestes dahinter: Der Code soll möglichst früh, möglichst klar und möglichst laut kaputtgehen, wenn etwas nicht stimmt. Genau darum geht es hier.

magicmarcy.de

Mon calendrier de l’avent – jour 18

Java est un langage qui a maintenant prés de trente ans, et qui en trente ans a subi un certain nombre de modes. Et certaines décisions initiales sont, encore aujourd’hui, considérées comme … houleuses. La plus douteuse est évidement la distinction entre checked et unchecked exceptions. Aujourd’hui, qu’on apprécie ou pas le concept, le consensus est que les checked exceptions ont échoué. Le problème, c’est qu’il faut vivre avec cette décision très structurante. Et dans le monde des lambdas, c’est vraiment pénible, parce qu’il faut mettre des try/catch partout. D’autant plus qu’en fait l’obligation de catcher les exceptions disparaît à l’exécution !

Heureusement, on peut résoudre ça simplement avec des projets comme throwing-lambdas. Celui-ci permet, en entourant votre lambda par un appel de méthode (qui ne fait rien) de faire disparaître l’exception checked de votre signature, et donc de faire les choses dans le respect de la lettre de Java. Et bien sûr, si une exception arrive, elle remonte tranquillement la pile d’appels.

En relisant mes notes dans Shaarli, je me rends compte qu’il y a enf ait un équivalent dans Apache commons lang : Failable. Alors laissez tomber throwing-lambdas, et utilisez plutôt Failable !

#exception #java

Why Checked Exceptions Failed

Programming language features are never orthogonal.

Fernando Borretti
I'm trying to #parse a string into an int in an #esphome lambda. I can use std::stoi() and it works, but I'm struggling at error management. It raises an #exception if the string is not parseable (i.e. "text" instead of "2"), but ESPHome disables the exceptions, so I can't simply try-catch it...
ATM the code is mostly working, but if the string isn't a valid int, the entire device crashes D:
How am I supposed to implement this?

#exception : or as to the decision of a judge, in the course of a trail, or in his charge to a jury

- French: exception

- German: die Ausnahme

- Italian: eccezione

- Portuguese: exceção

- Spanish: excepción

------------

Word of The Hour's Annual Survey @ https://wordofthehour.org/r/form

Word of The Hour - Annual Survey (2025)

Your responses to the questions below will directly impact the future of Word of The Hour. Your support and kindness has really meant a lot over the past three years. Thank you so much! Michael Wehar https://wordofthehour.org [email protected]

Google Docs

“Palestine Exception, #American #Exceptionalism: Two sides of the Same Bloody Coin”

by Benay Blend in The Palestine Chronicle

@palestine
@Palestine @[email protected]

“‘#Palestine #Exception’ serves as the most recent documentary exploring the wave of crackdown from college administrators, the media, police and politicians who oppose calls for a ceasefire and divestment from corporations that do business with ‘Israel’.”

https://www.palestinechronicle.com/palestine-exception-american-exceptionalism-two-sides-of-the-same-bloody-coin/

#Press #Israel #Gaza #Genocide #Zionism #Barbarity

... I just thought that something was too transparent between me and BTS you know. I've just got trauma, from when I needed to tell their Ghosts everything before we met. It was absolutely traumatizingly BORING to be so naked.

●. BTS are not allowed to read my Book, only with me.

#Exception: Yoongi, he needs Lessons

@tyil @SuperDicq @Vivaldi

“Generally a browser's most important thing is their engine.”

Think more, and you'll realise that #Vivaldi is an #exception. It's only #sellingPoint, as I said, is the #UI. There are many other #privacyFocused #browsers, #VivaldiBrowser's #powerfull #features are what keep it #afloat TBH.

"It's somehow fine for them to take the work of others, but this doesn't go both ways? Does this not sound a bit weird to you?"

If they make their work #available to be accessed by anyone, they'll die in the end. #VivaldiTechnologies is a much smaller company compared to #Google and #Mozilla.

"But even with Mozilla actively trying to make Firefox the worst it can be, the debloated forks are nowhere near as popular as the main thing, so your whole argument falls flat in reality."

No, it doesn't, because #FF was released much earlier than V. This means it had much more time to become #popular enough to keep it's #userbase, while Vivaldi wouldn't.

"forks are unlikely to become more popular than the main thing to begin with. They'd have to really fuck shit up to make a fork suddenly take all their marketshare, and at that point its just the market working as intended."

Yes, for more popular browsers. But for new ones, this is not true.