This is a pathetic excuse for introducing intrusive technology to solve a non-problem. If you think about it for a bit, it would be a simple matter to have a cop start issuing fines until the non-compliance rate drops to an acceptable level. This would cost nothing, as traffic cops generally collect far more in fines than their wages. Instead, our Dear Leaders want to use this situation to direct the indignant fury against cheaters towards promoting an array of face recognition cameras to track your every movement.*

* Of course, for this phase of the plan, they won't publicly acknowledge that the cameras are there to ID you as well as the number of people in your car.

Dump em!

It is 2015 and 90% of large enterprise have moved off IE 6 or use another browser like Firefox esr in their builds.

Did you know modern IE has compatibility mode! No really most incompetent admins use it now for adding IE 7 sites and later to the intranet zone. This means they can upgrade and emulation runs for older sites.

Banning IE 8 is almost there as you can remind them to install Firefox or Chrome which most should also have. Getting close indeed. It is not 2005 anymore where people have no other browsers

Well, sure, but here's a question for you:

What was the first version of Internet Explorer that included it?

Because the IE XMLHttpRequest documentation doesn't list it as a member. (I think that's the most recent documentation, but with MSDN, who even knows.)

And their example uses oReq.readyState == 4 /* complete */.

Then again, who knows when that page was last updated, and the standards they link to do include DONE. (And I checked: IE 11, at least, has it.)

My Data = My Property.

I posted a reply to a post by SirGeek.

Is the above sentence my data or yours?

Basically this. jQuery is one of those things that's almost literally bloat: it adds nothing that your browser can't already do, it just wraps around it. You absolutely do not need to use it.

However it saves on development time. It's effectively a bunch of boilerplate code that you don't have to deal with. It's one of those things that if you were to decide not to use it, you're likely to end up rewriting a chunk of it by the time you're done anyway, so you might as well go ahead and use it from the get-go and save yourself some time.

(Which isn't to say you should always use it. I've written pages where the amount of dynamic code was small enough that using jQuery would make absolutely no sense. But the larger your project gets, the more sense it makes to use frameworks like jQuery.)

You mean it's there now. Going back through previous version of the XMLHttpRequest spec, it wasn't added until June 2007.

Who knows when it finally made it into enough browsers to be safe to use. By now no one uses it more out of momentum than anything else, but it wasn't a part of the spec originally, and people writing tutorials would use "4" because that would work even in browsers that hadn't been updated to use the latest spec.

Michelle Slaughter
Earl Gallows
Trigger Winchester
Otis Hangem
Billy Bob Guilty

-

Aspartame has problems for some people (like my wife and brother-in-law) and not for others (like me).

Sucralose has problems for some people (like me) and not for others (like my wife).

Seems to me the thing for Pepsi to do is to bring out another formula - with a different name - using Sucralose, put them in the stores side-by-side (they get a LOT of shelf space to play with), and let the customers decide.

Changing the formula of an existing brand strikes me as a stupid move. I suspect Pepsi is about to have it's "New Coke!" moment...

Oh well, Diet Coke is still better anyways.

The radio story where I first heard about this claimed that Coke was considering doing the same to Diet Coke.

Must be nice.

In my world html5 comes in 2020 when Windows 7 Goes EOL

The bit you're apparently not grasping is something called a spatial light modulator. ... Couple it with a microwave radar or ultrasound sonar, and you can track individual raindrops and then cast shadows on them.

Then construct an object that appears to the system to be raindrops and you can put an invisible obstacle in the road. B-b

A site may wish to continue using JQuery because some of its clients are using older browsers that don't support the new features that allegedly obsolete JQuery code.

Drop the JQuery code and you drop those customers. Develop future code without it and the pages with the new features won't perform with people using legacy browsers. And so on.

I've seen similar things happen over several generations of web technology. Use care, grasshopper!

Unless you are ok with that app not working at times.

Web based is 105% crap when connectivity is flakey.

If you are making "free" apps, go for it, but if you are charging a customer $29.95 for the app, it had damn well better be a native app that works even with all radios turned off.

And I have a couple of $29.95 apps. Hell I have one for room audio tuning that was $59.95