| Agree in general that Elm is nicer than Redux. However... >>> You don't have to transpile or add a linter, or a type checker, or stitch new libraries every few months because the trend changed. Elm is still in alpha, and is adding and removing breaking features all the time. (See ports for example) [1] >>> No webpack or babel or eslint or immutable.js or typescript or flow or any of those. If you are integrating elm into any kind of existing application, you will likely need webpack. [2] >>> I doubt that learning "redux-sagas" will help me a year from now. Given redux is an order of magnitude more popular than Elm is, and Redux Saga is the most popular effects handler library for Redux, I would not agree with this statement. Learning about generators is valuable regardless. [1] https://github.com/elm-lang/elm-platform/blob/master/upgrade... [2] https://www.elm-tutorial.org/en/04-starting/03-webpack-1.htm... |
Elm has had 2 releases since 2015 which had breaking changes. The elm-upgrade[0] tool has automated away a lot of the upgrade progress, and the compiler tells you about all the remaining things that need to change.
Put another way, Elm doesn't actually change very often, and when it does, it is typically a smooth ride. (I've been around for 5 breaking releases, and all but one of them were very easy.)
> If you are integrating elm into any kind of existing application, you will likely need webpack.
If that existing application is already using webpack, then sure, you'll probably keep it. But you don't need it for Elm.
For example, we use Elm at work (on a 150,000 LoC Elm code base) and we actually moved away from Webpack because Elm doesn't need it and we weren't happy with its UX. :)
[0] https://www.npmjs.com/package/elm-upgrade