Apparently it’s not that the software is broken, it’s that the software being installed breaks Windows Update. There are reports from people that uninstalling StartAllBack, updating the OS, then reinstalling it back (renaming the install executable first) works fine.

As much as being affected by this is frustrating to me (though this is all happening still on the dev channel, so for me it’ll be a problem for the future), I understand Microsoft’s rationale here. They can’t be expected to support every third-party tool that can break the OS, and it’s known that both ExplorerPatcher and StartAllBack relies on many hacks using undocumented APIs to work.

In the last few decades that I’ve been using Windows, I never felt compelled to use shell replacements or customizations - the default experience always worked fine for me with a few tweaks. So, if anything I’m more frustrated at Microsoft that I’m forced to use StartAllBack, because MS went and removed options from the shell that existed forever and always took for granted, and then some.

Look, I despise Google as much as anyone these days, and I’m glad they’re taking a beating this time around, but at the same time, it’s also kind of bullshit. And it’s not even because you can sideload apps, or have alternate appstores on Android, but because we have yet to see the same standards being applied to Apple.

Chromium-based browsers still trounces Firefox on the Jetstream benchmark. I mean, I realize the Speedometer benchmark is supposed to test real-world scenarios, while Jetstream is more synthetic, but whatever work mozilla did to improve performance I’d expect to scale in other benchmarks too, so I’d expect Firefox to at least be bit closer to Chromium, even if losing a little.

Fair enough! FWIW, I also think your stance on the matter is fairly level-headed and well thought out, even if I’m more or less on the other side of the fence.

While I personally do not think that all Chromium browsers (especially since there are projects like ungoogled-chromium) transmit your personal data, I can’t verify this myself because the Chromium codebase is far too much of an undertaking for myself to review.

Don’t you think that, with so many contributors and projects having eyes on it (arguably more so than on gecko), if there was foul play wouldn’t anyone have sounded the alarm?