Remember the "Safari is the new IE" narrative? Just because Safari doesn't support some API doesn't make it IE, IE wasn't an inferior browser at the beginning either. What made IE the IE everyone hates was its departure from standards(?) and enforcing its own vision of the web thanks to its enormous market share. On IE's case, MS probably stagnated it to prevent competition against its desktop Apps business and on Go…
A list of recent hostile moves by Google's Chrome team
121–130 of 602 posts
Re: A list of recent hostile moves by Google's Chrome team
#122Remember the "Safari is the new IE" narrative? Just because Safari doesn't support some API doesn't make it IE, IE wasn't an inferior browser at the beginning either. What made IE the IE everyone hates was its departure from standards(?) and enforcing its own vision of the web thanks to its enormous market share. On IE's case, MS probably stagnated it to prevent competition against its desktop Apps business and on Go…
IE was absolutely hated for not evolving. I'm curious what "its own vision" was, other than "do as little as possible, while Mozilla and Opera keeps pushing forward." Now, this is from the perspective of the web developer. I don't think IE was ever hated the same way from the end-user perspective. Chrome is still innovating, but now end-users hate it, because it's trying to be too much. The "new IE" hat still belongs…
Re: A list of recent hostile moves by Google's Chrome team
#123Earlier quoted context omitted.
Oh interesting! Seems like a pretty specific requirement to have. Do you mind if I ask what you use those for? As for the tracking - I'm pretty sure Firefox blocks a lot of those by default, last time I checked it was plastered all across their homepage. It's not 100% effective, but if them making an effort to do the right thing pushes you away, you might be asking too much unfortunately. Building an entire browser t…
"Do you mind if I ask what you use those for?" Game engine. "As for the tracking - I'm pretty sure Firefox blocks a lot of those by default, last time I checked it was plastered all across their homepage" And the thing is, that firefox itself is tracking you and sends that data home. Maybe look up what "studies" mean. But so far at least you can opt out of it, unlike with chrome.
Re: A list of recent hostile moves by Google's Chrome team
#124Earlier quoted context omitted.
What would you think the problem with Firefox' UX that keeps so many people from switching is? I think it's not UX, but pure marketing.
People have all kinds of weird excuses for not using Firefox. Sometimes it feels like "Sure, Chrome sold my kids data to human traffickers. But I can't switch to Firefox because I really _need_ MIDI-2 over websocket support" Sure, FF is not perfect but a lot of issues is due to sites being optimised for webkit and that will not change as long as Chrome has 80% marketshare. You need to sacrifice a little for freedom.
I use Ungoogled Chromium.
Re: A list of recent hostile moves by Google's Chrome team
#125Expected a huge list and there's only 3 items there, and one of them, JPEG XL, is kinda moot because it didn't seem viable until recently after Safari started supporting it... Feel that the list could have had much more substance with the addition of webUSB, webSerial and such features which Chrome just strong armed. In the current form the list and toot don't really drive the point home...
Re: A list of recent hostile moves by Google's Chrome team
#126Firefox is unusable on Linux. Way too slow. But Brave browser is very snappy. It's the fastest chrome fork, and has great features, like vertical tabs, which have become essential to me.
Firefox isn't unusable on Linux but it should have first class performance and it's a shame it does not.
Re: A list of recent hostile moves by Google's Chrome team
#127Earlier quoted context omitted.
Frankly Firefox is barely a hedge against Chrome. When it comes to things like JPEG-XL they are in lock step with Chrome. Safari ended up being JPEG-XL’s unlikely champion. I kind of wished Apple would release Safari for other platforms again.
HN is weirdly obsessed with jpeg-xl. The logic for removing it totally made sense.
Re: A list of recent hostile moves by Google's Chrome team
#128Earlier quoted context omitted.
Yes, it's not a problem. For now. There are so many software projects that depend on chromium for their basic functionality, and so many users that indirectly rely on chromium. It's hard to switch to an alternative if the need arises. So when Google inevitably turns chromium into a problem, you don't have enough time to switch, no matter how badly you want to. It's time to preventatively switch to a project that's mo…
Most Chromium-forks are not interested at all (or do not have the resources, considering the tons of costs it has) into doing any core changes to fight against Google, only Vivaldi… all the others are either doing nothing or just PR bullshit. If a feature is rolled out to 95% of users, then websites have to adapt. If you have a browser and are part of these remaining 5% you will be the one blamed by the users and by…
If there isn't another option, you're stuck. We open ourselves up to horrific effects of browser monopolies like all the security issues that Microsoft didn't give a damn about back when internet explorer had a monopoly. It takes effort to switch to a different browser stack, like moving away from Chromium for example, but in the long term you do not want everyone stuck with only one option, because that will be even more costly.
Re: A list of recent hostile moves by Google's Chrome team
#129Remember the "Safari is the new IE" narrative? Just because Safari doesn't support some API doesn't make it IE, IE wasn't an inferior browser at the beginning either. What made IE the IE everyone hates was its departure from standards(?) and enforcing its own vision of the web thanks to its enormous market share. On IE's case, MS probably stagnated it to prevent competition against its desktop Apps business and on Go…
Re: A list of recent hostile moves by Google's Chrome team
#130Remember the "Safari is the new IE" narrative? Just because Safari doesn't support some API doesn't make it IE, IE wasn't an inferior browser at the beginning either. What made IE the IE everyone hates was its departure from standards(?) and enforcing its own vision of the web thanks to its enormous market share. On IE's case, MS probably stagnated it to prevent competition against its desktop Apps business and on Go…
IE was absolutely hated for not evolving. I'm curious what "its own vision" was, other than "do as little as possible, while Mozilla and Opera keeps pushing forward." Now, this is from the perspective of the web developer. I don't think IE was ever hated the same way from the end-user perspective. Chrome is still innovating, but now end-users hate it, because it's trying to be too much. The "new IE" hat still belongs…
Netscape had lame while IE had the very cool instead.