Many many moons ago, right at the beginning in this thread, you cited the example of GitHub ditching jQuery.
Hurrah!
In 2012 when, as a fairly experienced amateur coder, I first started helping out with the website of an NGO, I was told about jQuery. I'd never heard of it although I had started to dabble with JS, concerned only with how it worked on FireFox.
jQuery existed/exists primarily because of a deeply evil and chronically incompetent company headquartered in Seattle. At the time (2012) it was a question of either 1) learn and use jQuery or 2) accept the stench of excrement and humiliation that comes with having to familiarise yourself with what passes for M$'s implementation of JS. This, given that there are people on this planet who, offered the choice of using other free browsers, nevertheless, of their own free will and knowingly, choose to use M$ "products".
That's one end of the spectrum. When frameworks are good, or as close as possible to necessary.
Have you ever heard of/seen these US TV series called "When X go bad"... e.g. "When cops/helicopters/moms/serial killers, etc. go bad..."?
Good frameworks are a bit like that, IHMO: in Panglossian fashion, they start off with the best of intentions, in the Best of All Possible Worlds... but then they go bad (usually).
jQuery never went bad. It will never grow old. In the morning, and in the evening, we shall salute it. But it is the exception, not the rule.
Top comments (0)