Hacker News new | ask | show | jobs
by grzm 3510 days ago
I suspect the reason gp included the IE6 comparison at all was in response to yours, after looking into ES6 support across browsers for features you specifically called out, which I think is fair to do.

As for opening Chrome to post your comment, are you having issues with other browsers when you do so? I generally use Safari in Mac OS X and iOS without a problem.

1 comments

Web Developers use common lowest denominator with is IE8-IE9 for public facing projects and IE11 for internal...

Your Safari will work just fine, but it is still behind Firefox or Chrome [0]. I am not saying that Safari is new IE because we will struggle with IE11 for years to come.

Before Safari 10 ES6 was supported in 54% then in Safari 10 is 100%. This is wrong approach to web, it is the same approach that MS had in the past. Ignore standards and make some improvement with new version for bragging rights.

[0] https://nolanlawson.com/2015/06/30/safari-is-the-new-ie/

> Before Safari 10 ES6 was supported in 54% then in Safari 10 is 100%. This is wrong approach to web, it is the same approach that MS had in the past. Ignore standards and make some improvement with new version for bragging rights.

How is implementing some of a standard, and then completing work to implement 100% of that standard "ignoring standards"?

ggp: Also, the fact I had to open chrome in order to post this comment to HN is an amusing addition to this little "how broken is the web" discussion.

gp: As for opening Chrome to post your comment, are you having issues with other browsers when you do so? I generally use Safari in Mac OS X and iOS without a problem.

My comment on using Safari is in response to ggp saying Chrome was necessary to post to HN, not about general use or for development. Or am I misreading ggp?