4 ms·

Trying to compare these new Javascript solutions to creating "apps" as the "new jQuery" does a great disservice to jQuery. jQuery answered a great deal of the

by talmand 10y ago

Trying to compare these new Javascript solutions to creating "apps" as the "new jQuery" does a great disservice to jQuery. jQuery answered a great deal of the problems of the day in a way that abstracted away all the stupid stuff of the browsers we had to deal with. It didn't just make it easier to work with the DOM, it also made it easier to work with the browsers. These new Javascript frameworks and libraries address different problems than jQuery. Some provide solutions looking for a problem, in my opinion, but many provide solutions that jQuery doesn't even begin to address and should not. In a way, this comparison to jQuery also does a disservice to these other projects. None of them are the next jQuery, they are their own thing and should be treated as such.

true_religion 10y ago
Maybe they mean it in the sense of jQuery was part of the previous paradigm. In the new paradigm, React or Vue are the tools to use.
- talmand 10y ago
  I can see that, but in my experience none of these new frameworks or libraries have had the same impact that jQuery when comparing it to similar libraries of the time. When I came across jQuery that's what I started using and have never considered switching to anything else since. It's only recently that we can start laying off jQuery simply because the native APIs have finally started catching in terms of ease of use. As for modern frameworks like Angular, React, Vue, and so on; I have used multiples of them, and by the state of the community, I say they are fairly easy to transition from one to the next and none have had the same impact. I would imagine most reasons for changing is either job change related or just keeping up with the latest shiny thing. Heck, in some cases I still use jQuery with some of the new frameworks because it is still easier to do it that way.
  - k__ 10y ago
    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.
kedean 10y ago
The point he was making at the start is that it didn't matter that jQuery solved those browser incompatability problems (so did umpteen other libraries), it succeeded because it was easy to get started and build on. The problem being solved is not the matter at hand.
- talmand 10y ago
  I see the problem here. My main point isn't the problem that they solved, it's the impact they had on the industry. I say none of these new projects are having the impact that jQuery did. It's not a proper comparison that's beneficial to either side.

by talmand 10y ago

true_religion 10y ago

Maybe they mean it in the sense of jQuery was part of the previous paradigm. In the new paradigm, React or Vue are the tools to use.

talmand 10y ago
I can see that, but in my experience none of these new frameworks or libraries have had the same impact that jQuery when comparing it to similar libraries of the time. When I came across jQuery that's what I started using and have never considered switching to anything else since. It's only recently that we can start laying off jQuery simply because the native APIs have finally started catching in terms of ease of use. As for modern frameworks like Angular, React, Vue, and so on; I have used multiples of them, and by the state of the community, I say they are fairly easy to transition from one to the next and none have had the same impact. I would imagine most reasons for changing is either job change related or just keeping up with the latest shiny thing. Heck, in some cases I still use jQuery with some of the new frameworks because it is still easier to do it that way.
- k__ 10y ago
  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.

kedean 10y ago

The point he was making at the start is that it didn't matter that jQuery solved those browser incompatability problems (so did umpteen other libraries), it succeeded because it was easy to get started and build on. The problem being solved is not the matter at hand.

talmand 10y ago
I see the problem here. My main point isn't the problem that they solved, it's the impact they had on the industry. I say none of these new projects are having the impact that jQuery did. It's not a proper comparison that's beneficial to either side.