11–20 of 316 posts
If it works on Chrome, no one cares or even tests for other things.
If there is a JS feature in Chrome they want to use, so it’s impossible to use other browsers (instead of looking wrong) people do it.
Performs fine in Chrome? Ship it.
Yes, Chrome is the new IE in that it’s the only browsers companies care about, just like IE was for a very long time.
Everything has to be Chrome compatible to succeed. That’s the benchmark, not what the spec says.
Unlike IE, Chrome is still moving forward with new features and depreciating old features.
I blame lazy developers for this mess all around, which had caused a perfect storm of shit on the nouveau web.
Just to (mostly) preempt this because the exact same discussion is had every time this sentiment comes up: Isn't safari the new IE? Answer: They both are like IE, for different reasons: Chrome: Pushes proprietary extensions onto the web, which due to their absolute dominance others are somewhat forced to adopt, people develop for it and don't test in any other browser, just like IE Safari: is coupled to operating sys…
Unlike IE, Chrome is still moving forward with new features and depreciating old features.
Depreciating old "features" like supporting legacy OS versions which is infuriating. Firefox is an inadequate substitute because too many sites only work in Chrome. I blame lazy developers for this mess all around, which had caused a perfect storm of shit on the nouveau web.
Yes. If it works on Chrome, no one cares or even tests for other things. If there is a JS feature in Chrome they want to use, so it’s impossible to use other browsers (instead of looking wrong) people do it. Performs fine in Chrome? Ship it. Yes, Chrome is the new IE in that it’s the only browsers companies care about, just like IE was for a very long time. Everything has to be Chrome compatible to succeed. That’s th…
We've been through an extensive standardization pass for this to not happen. Anything not matching the specification whether in Chrome or any other browser should be considered a bug.
This is not at all the same as IE, where it just went its own way.
Just to (mostly) preempt this because the exact same discussion is had every time this sentiment comes up: Isn't safari the new IE? Answer: They both are like IE, for different reasons: Chrome: Pushes proprietary extensions onto the web, which due to their absolute dominance others are somewhat forced to adopt, people develop for it and don't test in any other browser, just like IE Safari: is coupled to operating sys…
If I understand - Chrome is like IE for pushing proprietary extensions, and Safari is like IE for not implementing those proprietary extensions?
Just to (mostly) preempt this because the exact same discussion is had every time this sentiment comes up: Isn't safari the new IE? Answer: They both are like IE, for different reasons: Chrome: Pushes proprietary extensions onto the web, which due to their absolute dominance others are somewhat forced to adopt, people develop for it and don't test in any other browser, just like IE Safari: is coupled to operating sys…
If I understand - Chrome is like IE for pushing proprietary extensions, and Safari is like IE for not implementing those proprietary extensions?
Earlier quoted context omitted.
If I understand - Chrome is like IE for pushing proprietary extensions, and Safari is like IE for not implementing those proprietary extensions?
Safari is like IE for not implementing standards everyone else has agreed on and implemented.
Yes. If it works on Chrome, no one cares or even tests for other things. If there is a JS feature in Chrome they want to use, so it’s impossible to use other browsers (instead of looking wrong) people do it. Performs fine in Chrome? Ship it. Yes, Chrome is the new IE in that it’s the only browsers companies care about, just like IE was for a very long time. Everything has to be Chrome compatible to succeed. That’s th…
> If it works on Chrome, no one cares or even tests for other things. We've been through an extensive standardization pass for this to not happen. Anything not matching the specification whether in Chrome or any other browser should be considered a bug. This is not at all the same as IE, where it just went its own way.
Should be, but isn't. At least not in a practical sense.