Chrome

Introducing the New Microsoft Edge →

December 3, 2019 · 12:43

Yusuf Mehdi:

The release candidate of the new Microsoft Edge for Windows and macOS can be downloaded right now with general availability targeting Jan. 15 in more than 90 languages. Microsoft Edge runs on the same Chromium web engine as Google’s Chrome browser, offering you best in class web compatibility and performance […]

We believe you should know who has access to your data and have the control to choose what you share. Microsoft Edge starts with tracking prevention on by default, so you don’t have to take any actions to immediately start having a more private browsing experience. With SmartScreen and Tracking prevention, we help protect you from phishing schemes, malicious software and new types of malware like cryptojacking.

I wish they’d chosen WebKit instead but at least Edge should be a decent alternative for people who need to use Google’s cursed Chrome.

Inside Microsoft’s Surprise Decision to Work With Google on Its Edge Browser →

May 6, 2019 · 22:08

Tom Warren:, writing for The Verge:

Something had to give. Microsoft had to change its Edge browser in a big way. That meeting with Nadella ultimately led to Microsoft’s huge decision to jettison the browser it built in house and start from scratch using Chromium as a new foundation. The stakes for success couldn’t be much higher: the future of Windows and the web itself could hinge on this project. 

This is the story of how Microsoft made that monumental decision and what could happen next.

I’m not personally interested in Edge or particularly happy that Microsoft joined the Blink/Chromium camp. I would have definitely been more please had they based Edge on WebKit or Gecko…

And speaking of WebKit…

I’m deeply disappointed in Apple for discontinuing Safari for Windows and not expanding to Linux and other operating systems. I don’t trust Google or Microsoft’s priorities (Google’s especially), and Chrome needs to lose some market share for our benefit. History has shown that a monopoly in the browser department doesn’t end well. Apple had the unique ability to challenge Google on competing desktop OSes and they forfeited that fight. Yes, Safari is holding its own on mobile. For now. That could change, when something new comes along, replacing our iOS and Android devices. At this point, all I can do is also root for Mozilla and Firefox.

Google Proposes Changes to Chromium to Kill uBlock Origin and uMatrix →

January 23, 2019 · 10:37

From the comments section:

From the description of the declarativeNetRequest API, I understand that its purpose is to merely enforce Adblock Plus (“ABP”)-compatible filtering capabilities. It shares the same basic filtering syntax: double-pipe to anchor to hostname, single pipe to anchor to start or end of URL, caret as a special placeholder, and so on. The described matching algorithm is exactly that of a ABP-like filtering engine. If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin (“uBO”) and uMatrix, can no longer exist.

Please don’t use Chrome (or Chromium unfortunately). Just switch to Safari or Firefox (I use it as my second browser and it’s fine). And while you’re at it, switch out your search engine to DuckDuckGo — it works surprisingly well, even in Poland when searching for Polish content.

via @khron

The Chrome Distortion: How Chrome Negatively Alters Our Expectations →

March 26, 2016 · 09:29

Chris Thoburn:

Chrome has taught us to idealize features for so long that we’ve become blind to its many glaring faults (…)

I’ve learned the hard way that Chrome is the new IE. I’ve learned that you have to architect an application well from the beginning for it to work well on all platforms. I’ve learned you can ship large ambitious JS apps to mobile, but it takes dedication and experience, and every trick you know to do it well for Android. I’ve learned that Apple loves the web, probably more than Google, and has invested heavily in ensuring we have a high quality platform upon which to build apps. But most of all, I’ve learned that we’re wasting a ton of effort right now trying to fix Chrome from the outside. We’re dancing around the issue; pretending that universal rendering, service workers, app-shell architecture, and keeping more of our applications on servers (where they don’t belong) is more than just a workaround for how bad Chrome is. Yes, these ideas have uses, merits, and probably are the future; however, our need and love of them right now is because our performance expectations have been badly distorted by the situation Chrome has left us in.