5 ms·

> Ultimately, I haven't actually used jQuery for anything serious in half a decade, and somehow I manage. I don't understand that sentiment ... Of course you c

by sgift 8y ago

> Ultimately, I haven't actually used jQuery for anything serious in half a decade, and somehow I manage. I don't understand that sentiment ... Of course you can "manage" without JQuery. JQuery itself doesn't use JQuery (D'oh) and somehow it can do all these things, so it is possible. The point of JQuery is that I don't have to think about the various (slightly) incompatible implementations of <whatever> in each browser version, but can just use one lib call and be done with it. JQuery to me is like using a car instead of running to another city. Yes, I could run, but why would I do that ..?

dangerface 8y ago
> The point of JQuery is that I don't have to think about the various (slightly) incompatible implementations Sure when jQuery was released in 2006, but browsers have had 12 years to improve their compatibility, and they have. Javascript has also had 12 years to improve and simplify its api, and it has. Your analogy was perfect for jQuery 2006 but in 2018 its more like buying a car to drive around the city or you can just take an Uber, you don't have to walk anymore.
- pjmlp 8y ago
  Tell that to those enterprise customers holding to IE 11, not allowing Chrome and doing their own timely releases of FF ESR.
  - GordonS 8y ago
    Where I work we only just upgraded to IE11 - it was a decent-sized project, involving a lot of people and manhours. I really wish we'd of just ditched it and moved to Chrome or Firefox :(
    - Spivak 8y ago
      So you would have a decent sized project involving lots of people and manhours, but without support from your vendor?
      - royce 8y ago
        If someone is developing web applications in such a way that they need support from their browser vendor to make them work properly ... they're doing it wrong.
        Spivak 8y ago
        I was assuming that the upgrade was more of an IT thing, that all the company computers are now on IE11.
        GordonS 8y ago
        Yes, that's correct. We have a portfolio of hundreds of applications, and needed to make sure every one worked OK on IE 11 before upgrading from IE 9.
- mercer 8y ago
  Also don't forget mobile browsers. I ran into a strange problem where Samsung's "Internet" didn't support something and could not find any online mention of this fact. (I wish I could remember what it was. Perhaps an array method).
untog 8y ago
jQuery to me is like riding a bike with training wheels attached after you've been riding for ten years. You don't need them, but unless you try taking them off you'll never know that. Browser incompatibilities are basically a non-issue these days for 95% of projects. Animations etc are far better done with CSS than jQuery (particularly when it comes to hardware acceleration). The Fetch API works in every browser. So on and so forth. I think the OP wasn't suggesting that "managing" without jQuery is difficult. Certainly, I can say that I haven't touched jQuery in years and haven't looked back once. There's nothing I miss.
- mariusmg 8y ago
  >The Fetch API works in every browser As long as you're using recent versions. The whole point of jQuery is that you can write some code and be sure that it will run correctly in older versions of the browsers.
  - blauditore 8y ago
    That's not the whole point of jQuery, it's just one advantage.
  - snarkyturtle 8y ago
    Well XMLHttpRequest has support going back to IE7.
- emsy 8y ago
  > jQuery to me is like riding a bike with training wheels attached after you've been riding for ten years. You don't need them, but unless you try taking them off you'll never know that. Why even use wheels when you can reinvent them? I'm not saying there are no reasons to go "bare metal", but satisfying your developer ego is not one of them. Unless you need every inch of performance or control, jQuery (or alternatives) is probably the more reasonable choice.
  - untog 8y ago
    Why would it be the reasonable choice when it was created to solve a problem that largely doesn't exist any more? jQuery wouldn't be created today in anything like its current form. It still lives on largely because of inertia. Using the APIs provided by the browser is in no way reinventing the wheel!

by sgift 8y ago

dangerface 8y ago

> The point of JQuery is that I don't have to think about the various (slightly) incompatible implementations Sure when jQuery was released in 2006, but browsers have had 12 years to improve their compatibility, and they have. Javascript has also had 12 years to improve and simplify its api, and it has. Your analogy was perfect for jQuery 2006 but in 2018 its more like buying a car to drive around the city or you can just take an Uber, you don't have to walk anymore.

pjmlp 8y ago
Tell that to those enterprise customers holding to IE 11, not allowing Chrome and doing their own timely releases of FF ESR.
- GordonS 8y ago
  Where I work we only just upgraded to IE11 - it was a decent-sized project, involving a lot of people and manhours. I really wish we'd of just ditched it and moved to Chrome or Firefox :(
  - Spivak 8y ago
    So you would have a decent sized project involving lots of people and manhours, but without support from your vendor?
    - royce 8y ago
      If someone is developing web applications in such a way that they need support from their browser vendor to make them work properly ... they're doing it wrong.
      - Spivak 8y ago
        I was assuming that the upgrade was more of an IT thing, that all the company computers are now on IE11.
        GordonS 8y ago
        Yes, that's correct. We have a portfolio of hundreds of applications, and needed to make sure every one worked OK on IE 11 before upgrading from IE 9.
mercer 8y ago
Also don't forget mobile browsers. I ran into a strange problem where Samsung's "Internet" didn't support something and could not find any online mention of this fact. (I wish I could remember what it was. Perhaps an array method).

untog 8y ago

jQuery to me is like riding a bike with training wheels attached after you've been riding for ten years. You don't need them, but unless you try taking them off you'll never know that. Browser incompatibilities are basically a non-issue these days for 95% of projects. Animations etc are far better done with CSS than jQuery (particularly when it comes to hardware acceleration). The Fetch API works in every browser. So on and so forth. I think the OP wasn't suggesting that "managing" without jQuery is difficult. Certainly, I can say that I haven't touched jQuery in years and haven't looked back once. There's nothing I miss.

mariusmg 8y ago
>The Fetch API works in every browser As long as you're using recent versions. The whole point of jQuery is that you can write some code and be sure that it will run correctly in older versions of the browsers.
- blauditore 8y ago
  That's not the whole point of jQuery, it's just one advantage.
- snarkyturtle 8y ago
  Well XMLHttpRequest has support going back to IE7.
emsy 8y ago
> jQuery to me is like riding a bike with training wheels attached after you've been riding for ten years. You don't need them, but unless you try taking them off you'll never know that. Why even use wheels when you can reinvent them? I'm not saying there are no reasons to go "bare metal", but satisfying your developer ego is not one of them. Unless you need every inch of performance or control, jQuery (or alternatives) is probably the more reasonable choice.
- untog 8y ago
  Why would it be the reasonable choice when it was created to solve a problem that largely doesn't exist any more? jQuery wouldn't be created today in anything like its current form. It still lives on largely because of inertia. Using the APIs provided by the browser is in no way reinventing the wheel!