Does it though? They are many longstanding bugs reported in their compiler repository, and this release doesn't seem to address any of them.
replyLongstanding issues that prevent usage? Not for me and the projects I’ve been apart of. No doubt there are plenty of reported issues, and no doubt they truly negatively impact some users, but I would still much rather choose the usability and stability of Elm 0.19.1-2 than anything in the typescript ecosystem today
replyWhen I worked on an Elm app in 2020, my users reported compatibility issues with various browser extensions (e.g. Grammarly, 1Password). I personally would prioritize making my apps usable for my users over making the DX usable for myself, so I stopped using Elm for future projects.
replyOh yeah those are a bear: grammarly, 1password, and darkreader were the big ones, but translation was too. Elm assumes it's the only thing modifying the DOM underneath its root element; the extensions assume the DOM is free to be manipulated. NRI did a writeup on how they fixed it. https://blog.noredink.com/post/800011916366020608/adopting-e... The TLDR is to use https://github.com/lydell/elm-safe-virtual-dom/
replyI agree that the stability is quite nice. But there are plenty of areas where the language could use some improvement - for instance, the ergonomics around writing nested Single Page Apps is pretty cumbersome.
replyWeird not to mention Elm's massive breaking change that killed the project?
replyHow does that bear on my comment?
replyBugs not being fixed is not a feature, it's a bug, and it's certainly not stability, it's just cope.
reply