4 ms·
why not flowtype/typescript+js es6+react+redux/mobx? currently a pretty nice reactive mobx-state-tree is on the frontpage of hn.
by botexpert 10y ago
why not flowtype/typescript+js es6+react+redux/mobx?
currently a pretty nice reactive mobx-state-tree is on the frontpage of hn.
- ggregoire 10y agoI'm quite sure it's exactly for that reason, not having to choose between - Flow vs Typescript - ES5 vs Babel - React vs Angular vs Vue vs jQuery - Webpack vs Rollup - Redux vs Flux vs Mobx vs React states etc... Plus, probably lots of dev prefer Elm's syntax and design.
- sgslo 10y agoParent is absolutely correct. I can either work on Elm and deal with breaking changes like variable declarations (as noted above), or work on my React/Redux app, where I'm halfway refactoring from ReactRouter v3 -> v4 and Redux Form v4 -> v6, both of which are painful upgrades. Which would you rather deal with?
- davidbanham 10y agoThis is exactly the reason I'm interested in Elm. My team has gone from React to React + Flux to React + Redux to React + Redux + Immutable to React + Redux + Flow in the last 2 years. That's a _lot_ of change, and we're not even talking about the build tool side of things with Browserify, Babel, Webpack etc. In Elm I can see the same kind of framework simplicity that attracts me to Go.
- q3r3qr3q 10y agoTypescript has types, but it's the same terrible language underneath.