Earlier quoted context omitted.
> This is what worries me. You only need to spend an hour on HN or Reddit to see that web devs couldn't care less about legacy browsers, even when most businesses need to support them. As I wrote, even if the whole core team insists on going 2.0 only at some point (high unlikely), it's not like it needs any highly technical skills for interested people to jump in and maintain 1.9. > I support the decision to fork jQu…
Don't get me wrong. I agree with you, and I don't think it's really a problem. Hell, if it is it's not a problem to use both libraries, and to serve 1.x to those using older browsers. It's just a shift in the core mentality of what people view jQuery as. Many of us use jQuery because it works, regardless of what browser a user is on. For a lot of others, jQuery IS JavaScript. If they want to do something on their sit…
Since open source is free and open, it really can't fuck you †. You can however screw yourself by relying on it to do your work for you.
As you say, few people have the skills, time and desire to fix these sorts of problems, and that means you can't rely on open source to fix them for you.
Fortunately, there is a simple solution to this called "money" which companies have and which can be given to a developer with the skills who will magically convert that money into the time and desire to fix the problem.
† If your company is willing to use open source, but only when it is perfect, and not willing to help improve it, maybe they are the doing the fucking?