Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Analytics to Drop IE8 Support at the End of 2013

thenextweb.com

Post reply on HN
Print view View original

11–20 of 36 posts

Re: Google Analytics to Drop IE8 Support at the End of 2013

#11

Post by jeremiep »

everettForth wrote: post #6

For those who aren't aware, IE8 doesn't support ECMAscript 5, which includes useful functions, such as: Array.prototype.map and Object.keys. The alternative to this is to use something like jquery's implementation of map. Anyway, this is why IE8 in particular is a cutoff for compatibility. A lot of startups are not building their sites to be compatible with IE8.

Why not just use underscore.js then? It uses Array.prototype.map for _.map if present and fallback to its own implementation otherwise.

Re: Google Analytics to Drop IE8 Support at the End of 2013

#12

Post by [deleted] »

everettForth wrote: post #6

For those who aren't aware, IE8 doesn't support ECMAscript 5, which includes useful functions, such as: Array.prototype.map and Object.keys. The alternative to this is to use something like jquery's implementation of map. Anyway, this is why IE8 in particular is a cutoff for compatibility. A lot of startups are not building their sites to be compatible with IE8.

[deleted]

Re: Google Analytics to Drop IE8 Support at the End of 2013

#13

Post by yuhong »

jeremiep wrote: post #11
everettForth wrote: post #6

For those who aren't aware, IE8 doesn't support ECMAscript 5, which includes useful functions, such as: Array.prototype.map and Object.keys. The alternative to this is to use something like jquery's implementation of map. Anyway, this is why IE8 in particular is a cutoff for compatibility. A lot of startups are not building their sites to be compatible with IE8.

Why not just use underscore.js then? It uses Array.prototype.map for _.map if present and fallback to its own implementation otherwise.

It is far from the only example (my favorite is the lack of XHTML support).

Re: Google Analytics to Drop IE8 Support at the End of 2013

#14

Post by dmethvin »

everettForth wrote: post #6

For those who aren't aware, IE8 doesn't support ECMAscript 5, which includes useful functions, such as: Array.prototype.map and Object.keys. The alternative to this is to use something like jquery's implementation of map. Anyway, this is why IE8 in particular is a cutoff for compatibility. A lot of startups are not building their sites to be compatible with IE8.

Unfortunately, Android 2.3 is not fully ES5 compatible either. Since that's about one-third of all Android I doubt that ES5 compat was the driving force for this move. More likely it was the non-W3C event model and general non-use of IE8 for the reporting interface.

Re: Google Analytics to Drop IE8 Support at the End of 2013

#15

Post by leokun »

dmethvin wrote: post #14
everettForth wrote: post #6

For those who aren't aware, IE8 doesn't support ECMAscript 5, which includes useful functions, such as: Array.prototype.map and Object.keys. The alternative to this is to use something like jquery's implementation of map. Anyway, this is why IE8 in particular is a cutoff for compatibility. A lot of startups are not building their sites to be compatible with IE8.

Unfortunately, Android 2.3 is not fully ES5 compatible either. Since that's about one-third of all Android I doubt that ES5 compat was the driving force for this move. More likely it was the non-W3C event model and general non-use of IE8 for the reporting interface.

Android users ought to just avoid the Android browser and use Chrome or Dolphin. I don't even understand why there is an Android browser. Android browser also has trouble with updating SSL cert authority information, and it's got issues with its touch implementation.

Re: Google Analytics to Drop IE8 Support at the End of 2013

#16

Post by yuhong »

leokun wrote: post #15
dmethvin wrote: post #14

Earlier quoted context omitted.

Unfortunately, Android 2.3 is not fully ES5 compatible either. Since that's about one-third of all Android I doubt that ES5 compat was the driving force for this move. More likely it was the non-W3C event model and general non-use of IE8 for the reporting interface.

Android users ought to just avoid the Android browser and use Chrome or Dolphin. I don't even understand why there is an Android browser. Android browser also has trouble with updating SSL cert authority information, and it's got issues with its touch implementation.

I think it predated Chrome.

Re: Google Analytics to Drop IE8 Support at the End of 2013

#17

Post by jessaustin »

leokun wrote: post #15
dmethvin wrote: post #14

Earlier quoted context omitted.

Unfortunately, Android 2.3 is not fully ES5 compatible either. Since that's about one-third of all Android I doubt that ES5 compat was the driving force for this move. More likely it was the non-W3C event model and general non-use of IE8 for the reporting interface.

Android users ought to just avoid the Android browser and use Chrome or Dolphin. I don't even understand why there is an Android browser. Android browser also has trouble with updating SSL cert authority information, and it's got issues with its touch implementation.

I figured it existed so device manufacturers and wireless providers would have something to crap all over, which wasn't Chrome.

Re: Google Analytics to Drop IE8 Support at the End of 2013

#18

Post by melling »

dmethvin wrote: post #14
everettForth wrote: post #6

For those who aren't aware, IE8 doesn't support ECMAscript 5, which includes useful functions, such as: Array.prototype.map and Object.keys. The alternative to this is to use something like jquery's implementation of map. Anyway, this is why IE8 in particular is a cutoff for compatibility. A lot of startups are not building their sites to be compatible with IE8.

Unfortunately, Android 2.3 is not fully ES5 compatible either. Since that's about one-third of all Android I doubt that ES5 compat was the driving force for this move. More likely it was the non-W3C event model and general non-use of IE8 for the reporting interface.

For many products, Google only supports the two most recent browsers versions for a given browser. IE11 will be out next month, so they should be dropping IE9 support too.

http://support.google.com/a/bin/answer.py?hl=en&answer=33864

It's probably just a matter of cost to support that much legacy.

As far as legacy Android, 2.3 usage will probably drop like a rock over the next two years. A 3-4 year old cell phone is going to be really out of date.

Re: Google Analytics to Drop IE8 Support at the End of 2013

#19

Post by giovannibajo1 »

drzaiusapelord wrote: post #10

This is interesting, because according the analytics I have access to, large institutions in my field (which is large in itself) seem to have standardized on IE8. I guess a lot of these shops went from IE6 to IE8, skipping 7 entirely. Its funny how long IE8 is sticking around and I wonder if its going to be the new "IE6" for some time.

XP extended support will end on April 2014. Antivirus will also cease support (most of them). This means that the day after, there will be a dozen of 0-days (currently being held) exploited in the wild.

I hope those organizations you cite have a plan for April. If they run XP, they must update. If they run Vista+, they can switch to a newer IE and use GPO to force IE8-mode for the intranet (if they wish so).

Re: Google Analytics to Drop IE8 Support at the End of 2013

#20

Post by selectodude »

leokun wrote: post #15
dmethvin wrote: post #14

Earlier quoted context omitted.

Unfortunately, Android 2.3 is not fully ES5 compatible either. Since that's about one-third of all Android I doubt that ES5 compat was the driving force for this move. More likely it was the non-W3C event model and general non-use of IE8 for the reporting interface.

Android users ought to just avoid the Android browser and use Chrome or Dolphin. I don't even understand why there is an Android browser. Android browser also has trouble with updating SSL cert authority information, and it's got issues with its touch implementation.

Android users on Android 2.3 can't use Chrome and Dolphin uses the native browser engine. I think Firefox Mobile would be your only option, but the performance has to be awful.
Post reply on HN