Comment by mikeryan | Hacker News Reader

Comment by mikeryan | Hacker News Reader

Parent Full thread

It sounds like an interesting but probably relatively common situation these - relatively experienced developers, but inexperienced where it comes to the front end, who are accustomed to working in a non-javascript language. In this case, sounds like it's python.

I'm a very experienced Front-End developer and a lot of the tooling questions still hit us in the ass. A few years ago we switched from a Backbone framework to React based with Reflux and Browserify. Within 6-8 months the mindshare switched to Redux and Webpack and now we're on to those. But its days to weeks to gain full understanding of those (Webpack is a slog) Unless your constantly keeping up to date every time you start a new project right now you're back to the drawing board on the current state of the React ecosystem.

I love React, I'm bullish on React-Native as well for a lot of use cases. I'll be happier once the community starts to lock in a bit better on a more consistent stack and I'm totally okay with their choice of Ember (curious on why this over Angular if they're doing a follow up ;-)

If you started with React a few years ago, then React would have been brand spanking new, so change shouldn't have been too surprising then.

The question is, have things stabilized now? There's some evidence it has: Redux & Webpack have had the mindshare for almost 2 years now. But a lot of people now recommend mobx over redux, the redux plugin situation is still evolving, react-router seems to have finally got things right with version 4, et cetera.

That being said, I think the above sounds more pessimistic than it really is. For example, redux vs mobx is really two different use cases IMO.

When you say "Redux plugin system", what specifically are you referring to?

I imagine packages that bridge react components with redux (react-redux, react-router-redux, redux-forms, redux-immutable). But I'm not sure to be honest.

> For example, redux vs mobx is really two different use cases IMO.

I wouldn't go that far, I'd say it's different ways of thinking about the same problem. Crucially, switching out your Redux stores/sagas for MobX stores should be a drop-in replacement for the most part. Actions are still actions, and stores are still stores. The only/main difference is that for MobX a reducer and an action are the same thing.

nice, can't wait to replace mobx with something new next year

Reply on news.ycombinator.com