5 ms·
Longstanding 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 ne
by auslegung 2mo ago
Longstanding 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
- sheept 2mo agoWhen 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.
- 1-more 2mo agoOh 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-elm-safe-virtual-dom https://blog.noredink.com/post/800011916366020608/adopting-e... The TLDR is to use https://github.com/lydell/elm-safe-virtual-dom/ https://github.com/lydell/elm-safe-virtual-dom/
- int_19h 2mo agoYou don't have to choose between Elm and TypeScript though, there are so many other options now - Haskell, F#, Rust, OCaml, just to name a few.