I was walking on the sidewalk at a traffic-lighted intersection when I heard a loud bang.
I turn around to see a Honda had rear-ended a Volvo 240 that had stopped at a red light. The front of the Honda looked like a piece of crumpled up paper wrapped up nicely on the 240's tow bar. The 240 was unscathed.
https://en.wikipedia.org/wiki/WebRTC#History
I don't think I could summarise it better than that Wikipedia section.
He also planned to have BcacheFS merged to mainline in 2018. Finally got it merged in 2023 (released in 2024).
Development will likely slow down a bit when things require more review, discussion and scrutiny now that it's mainlined.
I've recently switched from Firefox' vault to bitwarden.
I'd say it works 50% of the time. On desktop Firefox it just doesn't manage to autofill things some days and I end up copy-pasting my credentials.
On mobile is happy to present me with suggested logins for a page. If I have one, pick or generate one, then it's all dandy. If I decide I'd rather not, then there's no way out of that view. I end up force-killing Firefox mobile. Maybe the app works better than the browser extension.
Let me quote the Wikipedia page.
Bcachefs describes itself as "working and stable, with a small community of users". When discussing Linux 6.9-rc3 on April 7, 2024, Linus Torvalds touched on the stability of bcachefs, saying "if you thought bcachefs was stable already, I have a bridge to sell you", and in August of 2024 that "nobody sane uses bcachefs and expects it to be stable".
It's been being for a long time. It finally got merged to mainline in Linux 6.7. Sounds like they started a lot of renovations after that. It's still a bit too much in motion for me to consider it.
Performance and features look promising. I'll revisit in 2030 if things have calmed down and they still have maintainers.
I've been running btrfs for 14 years. It has similar features and a proven track record. It doesn't move as fast. That's a good thing for a filesystem.
GalliumOS is x86/64 only, and has been deprecated for years. Mainline distros have good support for the Chromebook quirks now.
Cadmium, on the other hand.
Did I misunderstand something about the scenario here?
Wordpress foundation is a non-profit that develops and hosts installation packages and updates.
WPengine is a for-profit company that sells wordpress hosting.
All WPengine installations constantly look for updates and download these from the wordpress foundation. I'd bet they probably rack up half of their bandwidth costs.
WPengine can of course freely use wordpress' GPLv2 licensed stuff, but it sounds like their leeching of resources was the main pain point.
To either contribute or host their own installation packages sounds like a fair request at the scale WPengine has been operating.
Hetzner, for comparison, sells virtual private servers running Debian. Debian is free, under a similar license as wordpress. Hetzner is a Debian partner and coughs up dough. Hetzner hosts their own mirrors to reduce load on Debian's repositories.
Be like hetzner. Stroke the hand that feeds, or are least don't tug at it.
Sounds like a prompt for generative AI to sink its teeth into.
edit: Here's a starting point if someone with photochop skills wants to bring it to the finish line.
these emulation handhelds – which often come pre-loaded with hundreds of games
I can only speak for the retroid pocket I have. It's not far off from a stock android phone, sans camera and modem, plus d-pad and sticks.
It only came preloaded with a few open source emulators available on play store for free in addition to GApps (with official play store support).
I thought identical twins usually had like a dozen of so diffing mutations by the time they reach adulthood.
I'm not familiar with 23andme enough to know if their markers would pick up on it.
WebRTC isn't necessarily a bad specification.
But that history shows how they draft a specification, implement a service around it at a fast pace (in this case even with a takeover), and many years later the draft turns into a än official specification.
Other browsers have no choice but to fall in line behind the draft if they want to stay relevant. And they did.
IE did the same shit with their marquee-tag back in the day. Last I checked it still works on Firefox. (It's still not in any w3c specification)