4 ms·

>I just don't find the idea that we have to move away from jQuery that self-evident. I think that there are always arguments made like this with any language/f

by batoure 13y ago

>I just don't find the idea that we have to move away from jQuery that self-evident. I think that there are always arguments made like this with any language/framework and the endgame comes down to where there is a use case there is a will. I recently participated in do a full webapp conversion from jquery to angular. One driver was a realization that jquery and related tools filled quite a bit of bulk in the platform(cutting them out the minified js ended up being 1/5th the original size). Another was a conscious decision to rebuild API first and angular provided a unique ability to very cleanly abstract a View/Service/Server type of architecture that has just never worked for us in Jquery. Plenty of people will continue to use JQuery just as plenty of people continue to develop in Perl despite other communities feelings that it does't fit their use case.

lerouxb 13y ago
Hold on. I'm not talking in a "Angular vs jQuery" way. I meant "Angular vs something like Backbone that just happens to use jQuery". I wouldn't build a large app straight on top of jQuery ;)
- batoure 13y ago
  See how quickly careless words can brand you as a sadistic maniac :) !!
- batoure 13y ago
  But seriously not to answer a question with a question, though I am going to... but maybe the better question is "why do frameworks like Backbone need to use jQuery?" Base angular is incredibly compact and I have yet to really run into a wall with it compared to projects we have tried to do in Backbone (that sounds like we have had problems in backbone we haven't I am just saying the experience is comparable). It seems to me like the best reason to keep jQuery in something like Backbone is to make it easier to integrate existing jQuery libraries... which is maybe worth reconsidering anyway.... see argument #1
  - delluminatus 13y ago
    Not sure about Backbone specifically, but jQuery is good for a lot more than DOM manipulation. It hides a lot of the differences in browser Javascript APIs, and provides a lot of convenient AJAX tools. For instance, server communication is as simple as a $.getJSON away.
    - batoure 13y ago
      so http requests are also similarly directly handled in Angular without the need for jquery.
      - verisimilidude 13y ago
        But his point stands: jQuery is useful beyond DOM manipulation as a library. In one of my current side projects, all of the DOM is managed through React, but I'm still using (and loving!) jQuery for all the $.ajax stuff.
        batoure 13y ago
        To be fair your statement is more inline with my first point, for as much as someone shows how clean Angular http services are there will always be someone who like the simplicity or paradigm of the more seasoned pillar platforms
AdrianRossouw 13y ago
we're kind of shackled to jquery, and it's really difficult to NOT use it. I think that the angular way is just cleaner, and less likely to break because it is pretty sensibly encapsulated. I suspect these libraries developed for angular, is a break from the past that the web is going to need eventually.

by batoure 13y ago

lerouxb 13y ago

Hold on. I'm not talking in a "Angular vs jQuery" way. I meant "Angular vs something like Backbone that just happens to use jQuery". I wouldn't build a large app straight on top of jQuery ;)

batoure 13y ago
See how quickly careless words can brand you as a sadistic maniac :) !!
batoure 13y ago
But seriously not to answer a question with a question, though I am going to... but maybe the better question is "why do frameworks like Backbone need to use jQuery?" Base angular is incredibly compact and I have yet to really run into a wall with it compared to projects we have tried to do in Backbone (that sounds like we have had problems in backbone we haven't I am just saying the experience is comparable). It seems to me like the best reason to keep jQuery in something like Backbone is to make it easier to integrate existing jQuery libraries... which is maybe worth reconsidering anyway.... see argument #1
- delluminatus 13y ago
  Not sure about Backbone specifically, but jQuery is good for a lot more than DOM manipulation. It hides a lot of the differences in browser Javascript APIs, and provides a lot of convenient AJAX tools. For instance, server communication is as simple as a $.getJSON away.
  - batoure 13y ago
    so http requests are also similarly directly handled in Angular without the need for jquery.
    - verisimilidude 13y ago
      But his point stands: jQuery is useful beyond DOM manipulation as a library. In one of my current side projects, all of the DOM is managed through React, but I'm still using (and loving!) jQuery for all the $.ajax stuff.
      - batoure 13y ago
        To be fair your statement is more inline with my first point, for as much as someone shows how clean Angular http services are there will always be someone who like the simplicity or paradigm of the more seasoned pillar platforms

AdrianRossouw 13y ago

we're kind of shackled to jquery, and it's really difficult to NOT use it. I think that the angular way is just cleaner, and less likely to break because it is pretty sensibly encapsulated. I suspect these libraries developed for angular, is a break from the past that the web is going to need eventually.