Unpacking Google’s new “dangerous” Web-Environment-Integrity specification

Techie@lemmy.world to Technology@lemmy.world – 760 points –
Unpacking Google’s new “dangerous” Web-Environment-Integrity specification
vivaldi.com
101

You are viewing a single comment

Why are you pushing Firefox when Vivaldi did the work of writing this article and Vivaldi has consistently been pro-user, pro privacy, and anti-google even while using Chromium as their backbone. Viva Vivaldi.

Using any chromium fork is supporting chromium as the default browser, and choosing gecko-based browsers means you throw your hat in the ring to show websites that not just chromium browsers visit them. Using a chromium fork also means you accept that google will dictate standards less harmful than web integrity. While it's not the end of the world, the last time this happened IE9 happened. Using Firefox means google can't simply decide to implement any spec they want and that spec becomes true because all user agents have it (exactly what is at risk of happening here. Vivaldi may make nice blog posts but if this ends up happening they'll be happy to implement it else risk losing their entire user base)

The would have been an argument to be made about performance but nowadays blink and gecko are pretty much at the same performance level.

Using a chromium fork also means you accept that google will dictate standards less harmful than web integrity.

Are these condescending statements how you intend to get people to switch to Firefox?

Death to chromium forked browsers. Vivaldi is chromium.

Because it's better to support a diversity of web render engines instead to avoid a situation like back in the days with IE.

I have used Vivaldi and even led my kid to use it, but I still always go back to Firefox and/or LibreWolf for peace of mind and extensions like uBlock Origin and Anesidora.

1 more...