4 ms·
Elm is pretty much dead at this point. The last substantial commits in the Elm repositories are about 2 years old. I liked Elm before, and was a great fit for
by cyberax 3y ago
Elm is pretty much dead at this point. The last substantial commits in the Elm repositories are about 2 years old.
I liked Elm before, and was a great fit for internal corporate applications. Something like an admin control panel or a monitoring tool.
Are there any similar projects that are in the "more alive" state?
- tikhonj 3y agoPureScript[1][2] seems pretty alive these days. From my relatively small, self-contained experiments, it's a lot more flexible and expressive than Elm at the expense of (maybe?) being a bit harder to learn up-front. [1]: https://www.purescript.org/ https://www.purescript.org/ [2]:https://github.com/purescript/purescript https://github.com/purescript/purescript
- azangru 3y agoHow has it been going for Purescript since its creator and maintainer Phil Freeman stepped down?
- bPspGiJT8Y 3y agoDidn't really change anything. PureScript is in goood hands of the maintainers and contributors currently.
- tazjin 3y agoThere were some Rust WASM frameworks that used similar concepts, I particularly liked yew. However yew has recently chosen a path more towards "magical" features instead of the simple Elm-style architecture. Don't know enough about the other ones to comment.
- AlexITC 3y agoIt's worth sharing Scala.js which has https://github.com/PurpleKingdomGames/tyrian https://github.com/PurpleKingdomGames/tyrian, an ELM-insired library for the UI.
- mejutoco 3y agoElm is pretty much finished (meaning feature-complete) IMO. Not much needs to be changed. I love Elm. I can always go back to a project and get back on it in 2 minutes. The compiler is superb. The problem is one must roll on their own almost everything. I dislike the constant churn of React and other libraries, that often add change for change's sake, and break backwards compatibility or depend on too many libraries. At the same time Elm is maybe too much in the other direction.
- incrudible 3y agoReact is also pretty much finished. I have not experienced breakage except in some exotic functionality. The churn comes from switching to hooks, but that can happen gradually and is not strictly necessary. Oh, and of course library authors like to break stuff, but that is not on React itself.
- mejutoco 3y agoBefore the switch to hooks there was the switch from class components to functions, but some features (error capture) were only available using class component. The router situation has always been a mess too, and passing props around and lately contexts also overlap and have changed with time. Some of building blocks seem to have been built organically, without regards for backwards compatibility. It is still very useful (I happily use react and next js) but the concepts are not very elegant and internally consistent IMHO.
- adamwk 3y agoIs there l10n and i18n support yet? I don’t know how a UI framework can be considered production ready let alone finished without support for string translations. Last I checked, after Elm 19 killed the third party wrappers around Intl I hadn’t seen any movement here, but maybe I missed it or this has changed since then
- paulddraper 3y agoReact doesn't have i18n
- cortesoft 3y agoDo all projects need to continue having work done on them to be considered 'alive'? Is there no possibility for a project to be 'finished' and still good to use without needing any more work?
- dudul 3y agoFor libraries wouldn't you expect at least work to keep supporting newer versions of the language? Or use the improvements brought by said new versions? For a language itself I don't know. I don't know I've never designed one. Maybe keep working on it to take advantage of improvements made to lower level libraries that you use?
- dustingetz 3y agoElectric Clojure - https://github.com/hyperfiddle/electric https://github.com/hyperfiddle/electric