33 karma · joined February 3, 2026
1. An Elm-like programming language that lives in .db files
2. A compiler from this language to strongly-typed database procedures in a target backend language
This has more in common with a semantic layer than an ORM.
What you gain is a shared language that connects the table definitions (say a SQL migrations folder) and your API language (often handwritten SQL). This can be type checked and optimized for you.
But for me the big question is what functionality do you lose? Can I express everything that PostgreSQL can?
However, Fontainebleau forest has many pine trees.
In fact there is an invasive caterpillar there that lives in pine trees https://en.wikipedia.org/wiki/Pine_processionary
The caterpillars are also a consequence of warming.
1. Convert the natural language proof steps into formal language
2. Pass it to the solver to verify the steps
Genuinely curious!
WhatsApp was on Windows Phone though.
Instagram was not on Windows Phone, which hurt it, but there is no indication it would have come to MeeGo either.
The points seem valid, however, and I will likely steer clear of Bun.
Valve gets it
What reassurance can you offer devs that are hesitant to try a new data-store?
What if this happens?
1. User makes a mutation
2. UI updates instantly
3. User closes the app before sync happens
4. User comes back and is surprised to see that their mutation did not actually happen
The loading / error / success states in a UI serve a purpose.
The numbers are not reliable.
If you are a 3:02 marathoner in normal shoes then run a 3:00 in a super shoe, you are still a 3:02 marathoner in normal shoes.
Are you sure? This is a feature of OCaml but not F# IIUIR
Edit: https://github.com/fsharp/fslang-suggestions/issues/538