Elm is the loveliest and easiest to maintain long-term language I have ever used, by far. People don’t know what easy to maintain really means unless they’ve come back to an elm project that’s years old that they’ve not touched in a long while. Adding new stuff or changing old stuff is a breeze.
And it’s bulletproof. You simply don’t get runtime errors. (Well, about a millionth as many according to one firm.) We’ve never seen one in production at my company, we only get any when we put them in with a debug trace, which elm only lets you compile in dev mode.
Elm compiles to javascript so started life as a front end only language, but you can use platform workers on the backend, but now there’s
elm-pages which is a thorough look at elm on the backend, complete with backend tasks and data sources.
(Honorable mention to elm-land which is to elm as next.js is to react. elm-pages started off as a solution in a similar space to elm-land, but has evolved into an elm-on-the-backend solution.)
The most paradigm busting and comprehensive solution to full stack elm is lamdera which is elm all the way and handles front end, back end and communication between them. Imagine your compiler automatically handled frontend/backend communication including encoding, transport & decoding, but also live version migrations of anything and everything, deployment, data encoding and persistence on the backend and even hosting, all very very robustly and reliably.
Anyone programming in JavaScript should have their programming socks privilege revoked.
Nothing wrong with a bit of JavaScript between two consenting adults 😌
name does not check out
Common confusion, I’ve never written a single line of python code in my life.
on the internet, no one knows you are a python, no one
I’ve been naughty.
You know the rules.
Hand. Them. In.
Only those who likes javascript.
Yeah some are sadly forced to write JS by the web 😔
This is why I love the Phoenix framework, I don’t have to write any JS and can still make a responsive webapp
Elm for the win.
Elm looks quite cool, how is it for full stack apps?
Elm is the loveliest and easiest to maintain long-term language I have ever used, by far. People don’t know what easy to maintain really means unless they’ve come back to an elm project that’s years old that they’ve not touched in a long while. Adding new stuff or changing old stuff is a breeze.
And it’s bulletproof. You simply don’t get runtime errors. (Well, about a millionth as many according to one firm.) We’ve never seen one in production at my company, we only get any when we put them in with a debug trace, which elm only lets you compile in dev mode.
Elm compiles to javascript so started life as a front end only language, but you can use platform workers on the backend, but now there’s
elm-pages which is a thorough look at elm on the backend, complete with backend tasks and data sources.
(Honorable mention to elm-land which is to elm as next.js is to react. elm-pages started off as a solution in a similar space to elm-land, but has evolved into an elm-on-the-backend solution.)
The most paradigm busting and comprehensive solution to full stack elm is lamdera which is elm all the way and handles front end, back end and communication between them. Imagine your compiler automatically handled frontend/backend communication including encoding, transport & decoding, but also live version migrations of anything and everything, deployment, data encoding and persistence on the backend and even hosting, all very very robustly and reliably.
Programming for an embedded system or microcontroller with a compiler that only does javascript
Nooo~