JDBC does not allow pipelining (a Postgres only feature).

It can reduce the number of db round-trips a lot, especially when using Supabase+RLS (or other systems that require frequent setting of configuration values that are basically fire-and-forget).

Meet Bpdbi, a library with first-class pipelining, which provides a Postgres db driver (that's binary only, as the legacy text-based protocol is no longer needed, it just takes up space) and exposes an API that's more close to Jdbi's that to JDBC's (developer friendly).

https://github.com/bpdbi

It has an extensive benchmark that shows it's on par or faster compared to other db connectivity stacks.

The resulting binary is, well, binary. Not Go. Or I miss something.

From what the community says, it's pretty stable (as in BW compatible).

I dont get your reasoning.

Adding `null` to C was very simple to add. It added a lot of complexity that the language designer did not see coming (hence the billion dollar mistake he made on that).

`NULL` was originally added to ALGOL back in 1965. C was not even a thing back then. It was obviously a bad choice to port NULL to C, one that ADTs would have perfectly modeled, without the billion dollar cost.

In fact C was built sometime around the early 70s, and at the same time the first MLs where also being developed. One added null, while the other added a better mechanism for "nothingness".

Bottom line is you cant compare "adding null" and adding a feature that is over 50 years old, one that is battle-tested thru generations, and still holds up.

Solid maths does no suffer bitrot.

ALGOL indeed. I stand corrected.

https://www.infoq.com/presentations/Null-References-The-Bill...

AI needs strong types just as much as human developers.

Strong types also improve the interaction between humans and AI: shitty code is way more obvious with strong types. Pure strong-type langs like Elm take this to an even higher level: all cases must handled, such that runtime errors are practically impossible to express.

I've worked professionally on a large Elm program that has had 5 devs on it, and the promise held out: no runtime error, ever. Other stories for this exist.

I think you have an interesting spot in the design space here...

Have you seen Lamdera? They have a way to use Elm on the server-side that is supposedly acceptable to the Elm-BDFL Evan Czaplicki.

https://lamdera.com/

This talk explains it well: https://www.youtube.com/watch?v=4T6nZffnfzg

Sky does all on the server (more popular lately with HTMX and LiveView), where Elm+Lamdera is basically 2 project and Lamdera ties you into a propietary-ish ecosystem.

Giving even a modicum of care of what Evan has to say in 2026 is a good joke. Only thing he's known outside the Elm community (aside from Elm) is how to antagonize your own community.