3 ms·

So, moral of the story is don't fix bugs because it might take a long time to make to the end user?

• clhodapp 14y ago
  No, it's that even after bugs are fixed in widely-used libraries, they will still exist in downstream projects and in the wild for quite some time. Given that jQuery exists to paper over implementation quirks (including upstream-fixed bugs) between real-world browsers, jQuery needs to worry these bugs long after they are fixed in the core library code.
• tolmasky 14y ago
  There is no moral, its just an observation of realities. From these circumstances judgement calls are made on a case by case basis. Maybe someday when all browsers have auto-update like Chrome it will absolutely make sense for everyone to focus their efforts on fixing bugs in the engine vs. writing workarounds. That is not the reality we live in today. I mean, I could argue that people shouldn't work around iOS bugs and should instead apply for jobs at Apple and fix UIKit itself so that everyone can best benefit from their labor. But that's absolutely absurd. It's also more than a little unfair to judge members of the jquery team for not going into a project like WebKit that's millions of lines of C++ and acting like they're coming up with excuses for "not fixing bugs". This is a symbiotic and healthy relationship, browser vendors benefit from groups like jquery that make those bugs livable today through workarounds so that their products can be more usable in the immediate and they can focus on the "real" fixes for the future. And don't forget that there are people who are running old OSes that would require buying a new computer before being able to upgrade their browser.