> If you opt-in for a flux architecture, you will
> soon write Java-as-in-the-90 on the frontend
> instead of Javascript, with so many adapters
> and design patterns as layers you will become angry.
I agree that teaching the complete stack is a pain. I guess there is `create-react-app` to help you there, but its scope is very small: you're not going to get static typing for example.
There is an "-er" somewhere at every step.
You pass callbacks here and props there, and then reference them the other way around. And then you plug stuff in your componentWillReceiveProps, or is it in compomentWillMount or componentDefinitlyDidMountISwear ? But wait this is a new style class, so you have to call super(props) in constructor insteat of getInitialState unless you have a super Esx plugin but then remember that your onClick callback need to rebind this otherwise you'll get 'attributeOnThis' is undefined somewhere in your bundle and you'll have a fun time.
When you come from flask, Django or Ror, having to deal with such API feels like going back to before the 2000 bubbles, where corporates tried to port their knowledge to the Web.
It does not feel agile at all.
[0] https://en.wikipedia.org/wiki/Fold_(higher-order_function)
All this has happened before. It will happen again
Hardly comparable to Java Servlets.
As soon as I get some work outsourced, here it comes yet another build system and yet another complete stack I have to get expert at.
Javascript lacks a standard library (a mistake from the beginning) as well as standard tools (can't blame Netscape for this, but today we could totally come up with something more definitive.
It sounds like you're looking for a full framework, e.g. Angular or Ember.