Explores how Hinduism's vegetarianism evolved, showing Java's meat-eating Shaivism and the social forces behind dietary norms.

Swordlash: > For me, explicitly tracking every possible error type at the type level is a huge overkill for very little practical benefit. It always reminds me of Java’s checked exceptions Right, but Java’s checked exceptions were terrible because firstly Java’s type system is terrible and gives no good way to abstract over exceptions and secondly because checkedness is a property of the exception’s type rather than a property of how it is thrown. Haskell with `ExceptT` etc. does not have those problems. Swordlash: > Most of the time, you either propagate errors or handle all failures in exactly the same way. And there’s a simple reason for that: most errors are either not recoverable at the point where they occur, or there’s only one sensible recovery strategy regardless of the error. But how do you know which type to catch or throw, if there’s nothing in the type that forces it to match the corresponding throw or catch?

This week's Java roundup for October 26th, 2026, features news highlighting: the GA release of TornadoVM 8.0; point releases of JNoSQL, Endive, JBang, JReleaser and LangChain4j; a maintenance release ...

The Key-Value data structure, most famously represented by Java's HashMap, is a secret weapon in any developer's toolkit. It has the power to transform compl...

The JDK's AOT cache promises faster startup for free, but in practice comes with a lot of issues. Here is what we learned using it for XPipe.

The JDK's AOT cache promises faster startup for free, but in practice comes with a lot of issues. Here is what we learned using it for XPipe.

The JDK's AOT cache promises faster startup for free, but in practice comes with a lot of issues. Here is what we learned using it for XPipe.