Tell that to those enterprise customers holding to IE 11, not allowing Chrome and doing their own timely releases of FF ESR.
Re:Removing jQuery from GitHub.com frontend
by GordonS on Thursday July 26, 2018 @08:46AM
(#17616978)
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 :(
Re:Removing jQuery from GitHub.com frontend
by Spivak on Thursday July 26, 2018 @09:29PM
(#17622799)
So you would have a decent sized project involving lots of people and manhours, but without support from your vendor?
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.
I was assuming that the upgrade was more of an IT thing, that all the company computers are now on IE11.
Re:Removing jQuery from GitHub.com frontend
by GordonS on Saturday July 28, 2018 @03:39PM
(#17634622)
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.
Re:Removing jQuery from GitHub.com frontend
by mercer on Thursday July 26, 2018 @11:19AM
(#17618133)
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).
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.