Echo JS 0.11.0

<~>
tracker1 3221 days ago. link 2 points ▲ ▼
While I agree with the sentiment... at this point the web development community is already very fractured.  Angular is still very strong in new business development, and React is just starting to edge in.  I'm not suggesting that we stop, but there is merit in sticking with React+Redux for a while.

In terms of features, universal rendering, and hot module replacement are important for iterative development.  React+Redux is at the leading edge of these features, well ahead of many alternatives.  Once the tooling for other options matures, I think it may be worth considering... for now, I'm a cautiously optimistic observer.

I will say there have been far fewer surprises with React+Redux than there have been with options that came before.  I don't mind OO syntax for components, but find that workflows work better in a more functional style.  It just depends on your needs.

Replies

qbert 3221 days ago. link 1 point ▲ ▼
There's _no_ merit sticking with React/Redux if you have a problem with how Redux works.

Frankly, it's easy to replace Redux with your own higher order component functionality - and you don't need Redux to do hot loading.
tracker1 3217 days ago. link 1 point ▲ ▼
The reason to stick with Redux, and related tooling is partially momentum.  It's a nicer/cleaner option imho than say full on flux (and similar), while much nicer as an option than Angular/Angular2, and likely to be able to see corporate buy in.

In the end, you still need to get support from other developers/management/business clients when writing anything, rewriting or changing architectures.