Re:Why Vue (Not React) Is the New jQuery
by k__ on Tuesday September 20, 2016 @05:25PM
(#12543567)
You're totally right.
Even if I never had to use jQuery directly (had a short gig with Ember) I can see what it did.
It made JavaScript usable in the dark ages and did it with a nice API.
What do the frameworks of today?
What is their USP?
I mean React, for example, has a nice small API and its component concept is easy to grasp. To create an app, simply nest components, but the boilerplate and understanding required for Flux/Redux obliterates this. Not to mention the whole BabelJSXFlow stuff they have going on (and try to solve with create-react-app now)
It can be rendered on the server and the client can show finished markup and take it over to form a SPA, but as far as I can tell this is mostly a querstion of taste, since it now forces more load on the server.
So I wouldn't say it had too much of a net-positive effect as it could have had.
Even if I never had to use jQuery directly (had a short gig with Ember) I can see what it did.
It made JavaScript usable in the dark ages and did it with a nice API.
What do the frameworks of today?
What is their USP?
I mean React, for example, has a nice small API and its component concept is easy to grasp. To create an app, simply nest components, but the boilerplate and understanding required for Flux/Redux obliterates this. Not to mention the whole BabelJSXFlow stuff they have going on (and try to solve with create-react-app now)
It can be rendered on the server and the client can show finished markup and take it over to form a SPA, but as far as I can tell this is mostly a querstion of taste, since it now forces more load on the server.
So I wouldn't say it had too much of a net-positive effect as it could have had.