 Reviews:
·AT&T Southwest
·Charter
| jQuery plans to drop support for IE Just to show what a lousy browser IE is and always has been, the very widely used javascript library, jQuery, had a meeting yesterday to discuss whether they were going to drop support for Internet Explorer versions 6/7/8. Doing so will greatly reduce the code size by eliminating all the hacks needed to get IE to perform correctly. Stuff not needed in far more modern browsers such as.....anything and everything else. |
|
 JAAuldeWeb DeveloperPremium,MVM join:2001-05-09 Hagerstown, MD kudos:3 | IE's suckage aside, you cannot be correct about this.
The jQuery dev meeting takes place on IRC on freenode in #jquery-meeting or in a Google+ hangout. The schedule is as follows:
MONDAYS: jQuery Core Dev Meeting: (minutes: »bit.ly/i3vsit ) WEDNESDAYS: jQuery UI Dev Meeting (minutes: »bit.ly/jqueryui-agenda ) THURSDAYS 2PM EST: jQuery Mobile Dev Meeting
Notice that there is no mention of such a thing in the jQuery Core meeting minutes as of the most recent meeting on 23 Jan. Any meeting which took place yesterday would have been about jQuery mobile, not the core jQuery. A discussion of dropping support for fairly recent versions of IE is plausible for mobile. There is no way, however, that jQuery core would just drop support for IE up through 8, although there is definitely a plan in place to phase out that support over time (as with any browser's older versions). -- The Yakabox | My Development Sandbox | LinkedIn Profile |
|
 cdruGo ColtsPremium,MVM join:2003-05-14 Fort Wayne, IN kudos:5 Reviews:
·Frontier FiOS
| said by JAAulde:There is no way, however, that jQuery core would just drop support for IE up through 8, although there is definitely a plan in place to phase out that support over time (as with any browser's older versions). Agreed. For our corporate site, over half our traffic is IE and half of that (25+% overall) is IE8 specifically. For a more generic, public site, Wikimedia's top browser version overall is IE8 with 12.7% with IE9 edging out IE7 6.88% to 6.06%.
I can not imagine that any discussion to drop support for IE was anything other then just a general roadmap if/when to drop support based on need or usage. |
|
 Tenar join:2008-01-02 Midland, ON | reply to howardfine I have no idea where that information came from.
Same story for me, IE users continue to be too high to ignore. |
|
 | reply to JAAulde Addy Osmani, a member of the jQuery team, tweeted about it on January 23. John Reisig mentioned it too but I forgot where. |
|
 DC DSLThere's a reason I'm Command.Premium join:2000-07-30 Washington, DC kudos:2 Reviews:
·Covad Communicat..
·Verizon Online DSL
| said by howardfine:Addy Osmani, a member of the jQuery team, tweeted about it on January 23. Nothing of the sort in his tweets or on his website. Something of that magnitude absolutely would be posted...not to mention there would be a raging debate all over the developmentsphere and statements from Microsoft. Niente. Nicht. -- "Dance like the photo isn't being tagged; love like you've never been unfriended; and tweet like nobody is following." |
|
 | »twitter.com/#!/addy_osmani Scroll down to Jan 23. He mentions it twice and references it throughout. One thing I didn't post was that support would drop in version 2.0. |
|
 DC DSLThere's a reason I'm Command.Premium join:2000-07-30 Washington, DC kudos:2 Reviews:
·Covad Communicat..
·Verizon Online DSL
| My mistake...went to his other feed. However, he specifically states that it is ONLY discussion being kicked around, and that IE6-8 support would be moved to a plugin if or when it was acted on.
Putting 6 & 7 out to pasture would be fine as long as 7 had at least nominal support. OTOH 8 & 9 are going to persist in meaningful percentages for at at least 2-3 more years. Dropping support for them would result in bloodshed since corporate developers have little to no choice as to what they must code for. No amount of purity preaching, indignant self-righteous pontification or beatdowns will alter that reality. -- "Dance like the photo isn't being tagged; love like you've never been unfriended; and tweet like nobody is following." |
|
 Reviews:
·AT&T Southwest
·Charter
| said by DC DSL:My mistake...went to his other feed. However, he specifically states that it is ONLY discussion being kicked around Yes. That's what I said.
My other point is how much baggage gets unloaded when they unload all the crap needed to make IE work. |
|
 DC DSLThere's a reason I'm Command.Premium join:2000-07-30 Washington, DC kudos:2 Reviews:
·Covad Communicat..
·Verizon Online DSL
| Probably less than what's in there to make all the versions of FF floating around work. Everyone bitches about IE but FF has become at least as much of a pain in the ass in the last 3 years. Every time they drop a new version, something has to break...next version might fix it but then something else is kaput. The frequency of updates makes the problem far worse than IE...I'm seeing FF as old as 5 still showing up in double-digits on some of the sites under me. And don't get me started about Excedrin Headaches #8192 and #8193 (iOS and Android)...this week has been a living hell here at the Galactic Command Center because of them. -- "Dance like the photo isn't being tagged; love like you've never been unfriended; and tweet like nobody is following." |
|
 Reviews:
·AT&T Southwest
·Charter
1 edit | said by DC DSL:Probably less than what's in there to make all the versions of FF floating around work. Absolutely not. He, or John Reisig, state specifically losing IE dramatically drops the load of code. Did he even say 50%? Don't recall. quote: Everyone bitches about IE but FF has become at least as much of a pain in the ass in the last 3 years. Every time they drop a new version, something has to break...next version might fix it but then something else is kaput.
No issues here but I don't know your situation. We've been using FF since 0.8 and now use FF and Chrome for initial testing of everything. We know stuff will break in IE cause, by far, it's the worst browser on the planet, as everyone knows, but the other two, plus Safari and Opera, never give us any real grief. |
|
 DC DSLThere's a reason I'm Command.Premium join:2000-07-30 Washington, DC kudos:2 Reviews:
·Covad Communicat..
·Verizon Online DSL
| You must be running in a far less diverse universe than my clients. Few of them are in the position where they can realistically dictate what can visit...even fewer have applications simple enough to avoid running into the ugly buried deep down in the current crop of non-IE clients. -- "Dance like the photo isn't being tagged; love like you've never been unfriended; and tweet like nobody is following." |
|
|
|
 cdruGo ColtsPremium,MVM join:2003-05-14 Fort Wayne, IN kudos:5 Reviews:
·Frontier FiOS
| reply to howardfine said by howardfine:No issues here but I don't know your situation. We've been using FF since 0.8 and now use FF and Chrome for initial testing of everything. We know stuff will break in IE cause, by far, it's the worst browser on the planet but the other two, plus Safari and Opera, never give us any real grief. Then you don't do any complicated designs. ALL browsers, regardless of which one, have quirks and issues. The more complicated your design or functionality, the easier those quirks and issues are uncovered. |
|
 Reviews:
·AT&T Southwest
·Charter
| reply to DC DSL We don't dictate what browsers can visit at all. We just code to standards and everything just works most of the time. Except for IE which uses up about 20% or more of our time getting standard code to work in it correctly, assuming it will work at all.
Most of our clients get a larger portion of their visitors from IE users but we have a few clients where its more Safari users. One of our sites gets a lot of IE users cause their biggest customer is a very large financial institution while several other sites are visited by people in the theatre or colleges/universities who most likely have Macs. |
|
 Reviews:
·AT&T Southwest
·Charter
| reply to cdru said by cdru:ALL browsers, regardless of which one, have quirks and issues. The more complicated your design or functionality, the easier those quirks and issues are uncovered. By "no issues" I mean nothing significant where we're tearing our hair out like you have to with IE. Our sites are generally ecommerce and some with pretty heavy volume. We're pretty bleeding edge so there's not much we don't have experience with. |
|
 usa2kBlessedPremium,MVM join:2003-01-26 Canton, MI kudos:3 Reviews:
·VOIPo
·WOW Internet and..
| reply to howardfine said by howardfine:https://twitter.com/#!/addy_osmani Scroll down to Jan 23. He mentions it twice and references it throughout. One thing I didn't post was that support would drop in version 2.0. Or FWIW more simply here? »twitter.com/#!/addy_osmani/statu···34664449 --
Jim, VoIP 12/2002, VOIPo 2/2007 FAH-Tool~Pets~Join Artist-247 |
|
 | Yeah. I don't remember how to do that type of linking. |
|
 cdruGo ColtsPremium,MVM join:2003-05-14 Fort Wayne, IN kudos:5 Reviews:
·Frontier FiOS
| said by howardfine:Yeah. I don't remember how to do that type of linking. Copy the url of the date link in the particular tweet. |
|