Hacker News new | comments | show | ask | jobs | submit login

Exactly. What does "several" mean? Are we talking two years? Five? A decade? Until jQuery changes their minds?

That last one. Given our past record on supporting things you shouldn't be too worried. But if you are, go to our GitHub project and click the Fork button.

Although I am probably just being a stupid person, I really dislike this argument "If you don't like it, fix it yourself".

While it might feel offensive that people are complaining left and right about the new version, it is actually a compliment. I am not trying to be a love-all hippie here, but people are complaining because they really fucking love the solution jQuery put out there to support multiple browsers.

Don't feel offended, feel proud.

I wouldn't call it "if you don't like it, fix it yourself." I'd call it "you need code that does X? We don't have that, but we have something that does 99.9% of X, and you can have it for free!"

Whereas if they said explicitly "we will support it for 5 more years" how would have changed anything? They can change their minds at any time, and it's not like you can sue them or anything.

Not to mention that the whole question is moot, for reasons I states on my comment above.

How relevant will IE8 be in just two years, though? If it's 3-5 which is what it sounds like, then that's just more of a nail in the coffin for IE8 support.

> How relevant will IE8 be in just two years, though?

That very much depends on your target audience.

For home users IE8 is pretty much dead already, the only subset of people stuck there are the few who are using XP and have not switched to Firefox/Chrome/other. As more and more game-y things on the web start demanding newer features rather than creating/using/supporting fallback options for IE8 (canvas in particular).

In more corporate environments, IE8 is often still king and will be for several years. Most of the clients for the product I spend most of the working day panel beating are large banks and most of them have only just migrated to IE8 from IE6 because they have to soon (IE6 falls out of extended support in less than 12 months, along with XP+sp3). If they follow the same pattern (and I see little reason why they won't, slow moving mammoths that they are) I and many others will have to be concerned about IE8 until at least 2018 as IE8 falls out of extended support in 2020 (as it's support windows are tied to Windows 7's). Hopefully jQuery's idea of "several years" is as least as long as this.

XP falls out of support next year: any bank using it would be going against very strong security guidance from Microsoft.

Once you're on non-antique Windows, there's nothing preventing you from going all the way to IE10 which, again, starts getting into situations where not upgrading for security reasons starts approaching negligence.

> XP falls out of support next year

But Vista and 7 do not, and you can can run IE8 on them just fine. IE8 itself is supported as long as Windows 7 is, which is Janurary 2020 for the extended support phase.

> Once you're on non-antique Windows, there's nothing preventing you from going all the way to IE10

Nothing. Nothing at all. Unless you consider a large collection of legacy applications that either just plain don't work in anything other than legacy IE or simply haven't been tested (and signed-off as compatible and SLA-covered by the supplier) in anything else.

They can't take the risk of not getting getting those apps thoroughly tested before upgrading and that will cost money (as will any changes, or complete replacemets, needed) and more importantly a huge amount of time (nothing moves quickly inside a bank no matter how hard enthustic and/or concerned people push - organisations of that size have trouble working up the inertia for significant internal changes).

My suggestion has always been to install something else alongside IE and migrate that way: keeping IE around for those applications that require it (or have not been signed-off as working well on something else) but having something better for applications that don't rely on "classic" IE's excetricities. I get funny looks for that suggestion though - the thought of training users to cope with two programs where they once had one seems to trike TS people cold.

> approaching negligence

One of the key drivers working against building up change inertia is fear of neglidence (or accusations there-of). Large organisations have a significan aversion to risk, organisations within regulated industries (where you may do more than fail: you may fail and pick up a hefty fine and/or loss of license along the way) in particular, if they were people you'd probably call them neurotic on the matter. Change without sufficient plannig is a form of negligence, and fear of this is a large part of what adds friction to any forward movement.

Excellent opportunity to start a company with a paid support model.

IE8 dropped under 10% for me last month. Several years seems fine to me.

Well then, be sure to let us know which browsers we should be worried over supporting with your analytics from a few years from now.

Try Akamai's global CDN stats showing similar numbers:


Ok, what if my analytics disagree with their analytics? That was my point. Every website's needs will be slightly different than others. The point is that someone saying "I don't need to support browser X" doesn't mean that everyone else can stop supporting browser X.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact