• 0 Posts
  • 21 Comments
Joined 2 years ago
cake
Cake day: July 25th, 2023

help-circle
  • Really bigger updates obviously require a major version bump to signify to users that there is potential stability or breakage issues expected.

    If your software is following semver, not necessarily. It only requires a major version bump if a change is breaking backwards compatibility. You can have very big minor releases and tiny major releases.

    there was more time for people to run pre-release versions if they are adventurous and thus there is better testing

    Again, by experience, this is assuming a lot.









  • Which generation is that? I’ll be honest, I’ve yet to talk to someone who really gives a crap about where the content they’re consuming is coming from. Hell, most people I’ve dealt with don’t give a crap about content being pirated whenever it happens to be the more convenient option.











  • Thing is, we’re not in that hypothetical world, we’re in a world where Google has a near monopoly on the browser space, and controls and steers the very project most of the others use as a base. In this context, I don’t think it’s particularly hard to see how the Chromium hegemony is hurting the browser landscape.

    The view on “just don’t use it” is a bit more nuanced than that. For example, Manifest V3. Deciding not to use it means those browsers would have decided to completely break Chrome extension support in their browsers. Keeping it would also have meant literally re-implementing V2 support in their browser as it would be gone from the mainline. So what can browsers realistically do other than fold and adopt V3?

    The mainstream usage of features can come from Google themselves. I’m thinking for example of the old YouTube Angular redesign, which used a pre-standards V0 Shadow DOM API that was only ever implemented in Chromium and relied on a very slow polyfill everywhere else, which resulted in majorly degraded performance on one of the most visited websites on the internet for anything that was not their own browsers.

    “This site was optimized for Chrome” is only gonna get worse.


  • Google controls the Chromium project. They decide what gets merged in or not. The other browsers are basically soft-forks. They can rip stuff out after the fact, but they can’t stop Google from merging stuff into Chromium in the first place.

    I’d argue Chrome’s marketshare may not have been as high as it is right now if every browser out there didn’t cave in and become Chrome-in-disguise.

    Don’t get me wrong, I still use Chromium browsers for a bunch of stuff, but its hegemony on the web and the fact Google doesn’t have to wait for anyone’s approval before merging their shit is basically turning Chrome into the new IE.