HTML5 vs XP IE8 ???

2 days ago, fanbaby wrote

...these developers/managers are holding it wrong...

...the rug should be pulled from under them....

There are a lot of big organisations with big internal websites that were made in the early 00s. Indeed governments (and there are lots of them) that routinely put out invitations to tender that specifically mention that the site must work under IE6/XP but no mention of other browsers.

You can just pull the rug out from under them, but let's not forget that Microsoft makes most of its money from corporate customers, not from end-users. Pissing your customers off isn't a good way of making money.

2 days ago, steve01 wrote

XP/IE8 user need to go away anyway, right?

We agree.(Yes, I do detect a hint of sarcasm) [Edit: Oops, bad click on my part]

I don't think I would knowingly buy a product that I knew my customers would be unable to use unless I had plans to get them off of XP/IE8. To forge ahead anyway seems like a very bad idea.

6 hours ago, evildictaitor wrote

*snip*

There are a lot of big organisations with big internal websites that were made in the early 00s. Indeed governments (and there are lots of them) that routinely put out invitations to tender that specifically mention that the site must work under IE6/XP but no mention of other browsers.

You can just pull the rug out from under them, but let's not forget that Microsoft makes most of its money from corporate customers, not from end-users. Pissing your customers off isn't a good way of making money.

I kinda understand that, but the problem as I see it started when someone promised backward compatibility. That's nice and all, and it made Microsoft what it is, but that's not the web. The web has no allegiance to no st!nk!ng backward compatibility. Its only allegiance is to standards. Yeah, I know they are shitty and suck (so say Silverlight disciples) but they are mine! And yours. ANd they are all we got.

The web. No entrance for:

1) Backward compatibility seekers. Just use a native Microsoft app already.

2) Lost pixel seekers. Use fncken PDF.

The two of you, I hate you  

Interestingly, one of the most widely used JS libraries - jQuery - is dropping support for IE6/7/8 from V2.0 onwards - due for release next year (I think?). They claim that removing all of the hacks required to support these versions of IE dramatically reduces the footprint of the library and improves performance.

jQuery 1.9  will be the last version to support so-called 'legacy' IE

@ kettch

I did say i didnt RTFM, and i do now have written a HTML4.01 page presenting the same things for the IE8 users. 

@elmer

from JQuery's blog:

Why is the jQuery core team dropping support for oldIE (IE 6/7/8)? We're not! jQuery 1.9 will support oldIE when it's released next year. The jQuery team will continue to support and maintain version 1.9 even after jQuery 2.0 is released.

How long will you support jQuery 1.9? As long as oldIE is a significant factor on the web.

Even the old JQuery versions works real fine that problably most sites will use for years to come.

@Steve01

As I said:  "jQuery 1.9  will be the last version to support so-called 'legacy' IE"

At the 1.9/2.0 branch, the functionality will be the same, and 1.9 will be maintained for bug-fixes.

However, from that point onwards (version >= 2) jQuery will NOT support legacy IE and this means that future development on jQuery will not support IE6/7/8

What they are saying is, that if you need Legacy IE support, you can continue to use versions up to 1.9, but that all development beyond that point will be without IE6/7/8 support.

@elmer: Which, ironically, is what MS did with IE8 itself, and that is what steve01 was complaining about ...

Herbie