Re:Why Elm? [pdf]
by canadaduane on Monday May 08, 2017 @04:04PM
(#14295073)
Yes, this is a problem IMO. I dedicated 9 months to learning Elm, but left frustrated by the tight control and lack of delegation that would have leveraged my skills and many others' skills to further the idea and language.
On the other hand, it's easier to wait patiently if you're not using the language yet :-)
I've been watching Elm for some time. I'll wait until it's done. So my reason for not using Elm is: I'd rather be patient.
Re:Why Elm? [pdf]
by KurtMueller on Monday May 08, 2017 @05:16PM
(#14295680)
I think you're going to be waiting indefinitely then :).
The elm language/framework designer is planning 10 years ahead. At least it's ambitious!
For everyone who need to write SPAs right now (or in 2 years) it's just meh.
In 10 years, the proverbial puck will have moved. Language ecosystems where the BDFL doesn't learn to delegate wither and die.
Yes it will.
So it's really good at what it does, but for everything else, it's just incomplete. For instance, Elm seems like a natural fit for an offline-first ServiceWorker design. But I don't think it really covers much of the just-outside-of-core-Javascript browser APIs. You're likely to run into "I have some really interesting ideas about how to cover that a super elegant way, but I'm concentrating on rewriting the $WHATEVER right now" newsgroup posts, but that's it… :-(