3 ms·
I'm extremely keen to see what the SQL<->Elm experience might be (assuming something like that is part of the deal too). Simplifying how we interact with databa
by refset 3y ago
I'm extremely keen to see what the SQL<->Elm experience might be (assuming something like that is part of the deal too). Simplifying how we interact with databases is arguably even more important/$valuable than simplifying UIs.
- carapace 3y agoFWIW, I'm about to try integrating Elm and Tau Prolog (Prolog-in-JavaScript). I have a toy language that uses Elm for the interpreter and Prolog for the type inference and I want to make one of those nifty "try this language right in the browser" things. The "relations" in Prolog and SQL ("relational model") are the same thing, and Prolog is arguably "nicer" than SQL? https://en.wikipedia.org/wiki/Relational_model https://en.wikipedia.org/wiki/Relational_model
- 1-more 3y agoI strongly endorse having some fun with Lamdera then. Your frontend and your backend are written in Elm. Your backend state is the state of the world, and it is stored in a DB. You write migrations that force you to have a safe translation between versions. They answer the question of "given a state of frontend and backend models and in flight messages, how do we construct new versions of these things?" And they can include "throw out that message" if you really want.