Elm is also unstable; there's no guarantee Evan won't break things in the next release.
It's a bad combination. A fork could in theory fix this. Has anyone done it, though?
> no release since October 2019
Three years with literally not changes is pretty stable in the fronted world.
The known bugs are not a huge blocker for most people.
Even if a new version with breaking changes would arrive tomorrow you could still keep using the version of Elm that worked fine for years. Really no issue.
They get it! Especially the being able to run your program even with compile errors part. Looking at you Golang and Zig with your unused variable errors. Let me do my prototyping!
And yeah, Richard Feldman is awesome. Roc is sure worth keeping an eye on.
There are. I have never encountered them in my life but yeah there are. Fork it if they're really holding you back
> Elm is also unstable; there's no guarantee Evan won't break things in the next release.
I'm showing my privilege as someone who started with elm with 0.19 after all the big emergent patterns had emerged, but here goes: the FFI workaround that was broken from 18 to 19 was telegraphed for years. Earliest mention about it being disfavored I can find is from 2015 [1]. Conversely with 0.19.1 we get "If you like what you see now, that's pretty much what Elm is going to be for a while." [2] Ports and Custom elements make it such a non-issue to interact with JS while keeping your state in elm that it's just never held me back shrug.
> It's a bad combination. A fork could in theory fix this. Has anyone done it, though?
Gren, Derw, and eventually Roc compiled to JS/WASM could all do it I guess. Remains to be seen, but it's a very exciting space right now. It's a bit like The Velvet Underground: they only sold 20k records, but everyone who bought a copy started a band (or so the saying goes).
[1] https://groups.google.com/g/elm-dev/c/1JW6wknkDIo/m/H9ZnS71B... [2] https://github.com/elm/compiler/blob/master/roadmap.md
If you are building an SPA then there is always Mint[1] (it's an Elm like language).
[1]: https://github.com/mint-lang/mintTraining developers is expensive. The less experience they have, the more expensive it is (generally).
> Elm is simple, write your own compiler.
The economic argument against this is it isn't easy (expensive) to write and maintain your own compiler.
https://elmprogramming.com/interacting-with-web-components.h...
Or to use web components https://elmprogramming.com/interacting-with-web-components.h...
If a technician can handle a job, why would I hire a programmer?
> programming new editing commands was so convenient that even the secretaries in his [Bernie Greenberg] office started learning how to use it. They used a manual someone had written which showed how to extend Emacs, but didn't say it was a programming. So the secretaries, who believed they couldn't do programming, weren't scared off. They read the manual, discovered they could do useful things and they learned to program.
https://www.gnu.org/gnu/rms-lisp.html
Our (programmers) whole business model is predicated on the normies not realizing they don't really need us.
From that POV the JS ecosystems and all their churn are a form of job security. I feel like it's kind of a scam, a Potemkin village of complexity to hide the fact that computer programming just isn't that hard, and most needful software is already written.
(Excel is the most successful programming language and IDE in the world, eh?)
You trade in some purity for practicality. Elmish on the front end is really nice. You get F# on the back end. Fable remoting makes RPC front end to back end really easy. The docs are amazing https://zaid-ajaj.github.io/the-elmish-book/#/.
You get access to the .Net ecosystem so it enterprise ready.
Instead all I got is "Trust me, it works", just like all the other snake oil salesmen on the street.
Is this not a valid objection? Surely there is a non-trivial economic cost associated with have a dickhead maintaining a critical part of your stack, who's willing to remove support you rely on at his whim.
> Elm is simple, write your own compiler.
... that is a significant economic cost; which if you have a non-trivial probability of having to do, drastically shifts the cost/benefit analysis in favour of JS.
I've been challenging folks for a while now: What's the economic argument for using JS in a world where Elm exists?
In other words, if you want a front-end app, and you do not care about the technology used to make it (you're not using a particular stack just because you like it) then you should pretty much just use Elm, eh?
If I'm some business owner who wants a web app that works reliably and is cheap to maintain, I don't know or care about the underlying tech stack, it seems like Elm is sooooooo much better than all the JS frameworks and "ecosystem" in terms of the metrics I care about.
Typical objections:
1) JS devs are easier to find.
I would never hire a programmer who can learn and use JS but refuses to learn and use Elm. That's a technician not a programmer.
It's easy to train non-programmers to use Elm. (If you can solve Sudoku you can learn to program.)
2) Elm doesn't integrate with some library or service.
That's an argument for wrapping that lib/service in an Elm module, not against using Elm entirely. (E.g. in Rust you sometimes must use unsafe code but we do not give up the borrow checker entirely.)
3) Evan is mean.
I do not care.
4) I can't control the Elm compiler development.
Elm is simple, write your own compiler.
- - - -
I've heard that there's work on an Elm-to-native app compiler... Neat.