Probably because they’re building their own engine from scratch. Many of the popular browsers these days are built on Chromium or Webkit. The only “big” alternative these days is Gecko, which is what Firefox uses.

This matters because Chromium based browsers make up the vast majority of usage and Google has been using Chromium to drive web standards in the direction they think they should go.

Wikipedia has an overview, but doesn’t really cover Chromium’s market capture. https://en.m.wikipedia.org/wiki/Comparison_of_browser_engines

Agree. The default download location on iOS and padOS is iCloud and it’s pretty clear that Microsoft is chasing Apple’s monetization model.

Haha, TIL that SQL is 51 years old. IBM mainframes were still all the rage in the 70s. My assumption is that government would have not been an early adopter, but I could obviously be wrong.

That sounds surprising modern. That’s good! Or at least I would think it is good. So many things run on mainframes still.

We have a test environment but it’s a hot mess. All the data is made up and extremely low quality. All the things you would normally interface with are also in test, but getting other teams to coordinate testing in the test space is… a chore. We do the best we can with mock services, but without having real services or representative data some of the data pattern assumptions don’t play out. Leaders value writing code and our lack of architects that span teams mean that when team architects either don’t meet ahead of time, make assumptions, or don’t ever agree on a design then…

We always host UAT. We also track logins. Guess how many users even show up for UAT, let alone actually click on anything.

This is why the vast majority of our testing happens in prod when our users are doing real work.

Sorry for the baby rant :)

This can also be one of the frustrating parts of open source.

Find something you don’t like? Fix it. Will the repo owner approve your pull request? Who knows. Maybe they’re a bit absentee. Maybe they view the original behavior as working as designed. Maybe your design doesn’t fit their architectural model, so they’ll (eventually) heavily refactor your changes and merge them in.

You can always stand up a fork, but keeping those two at feature parity and going in the same general direction can become harder and harder with time.

That’s not to say not to try! But it also means reaching out to the repo owners/maintainers before making your first change.