Hacker News new | past | comments | ask | show | jobs | submit login

IEfication isn't really about oppression tbh, it's about Websites telling me "This application only works in Google Chrome" and completely locking me out. And they work in Firefox once you spoof the useragent. If they don't it's 99/100 times because Chrome is not being spec compliant or doing something dumb. Rarely because Firefox simply doesn't support it.

Having only one browser in the market/ecosystem is dangerous, we learned that with IE.




That has nothing to do with Chrome. It's bad (horrible!) web developers and their product. You can't blame Google or Chrome for that.

Good web developers create sites built toward standards, not browsers.

I occasionally read of people who claim such sites exist, and I'm sure they do, but I have as yet to find one while living on the web all day. (I'm a web developer.)


I blame Google and Chrome. Because Google continues to push for marketshare. If their devs were good devs they would strive for a balanced marketshare, not domination.

This is obviously not what Google is doing, therefore I blame them just as much as the web devs.

If you want an example, though recently fixed after I sent of a very angry complaint, the ELSTER tax system in Germany didn't work if you had a certificate login on Firefox+Linux but it worked on Chrome+Linux.

Another example is some of google's own websites, which break U2F authentication at times, though it might have been fixed in the meantime.


> You can't blame Google or Chrome for that.

Google themselves are building "Chrome-only" websites.

https://www.theverge.com/2018/1/4/16805216/google-chrome-onl...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: