That’s fair, I assume most people probably aren’t following ladybird that closely so it’s easy to miss. It just bothers me because shrugging off small individual problems and ignoring a bigger trend is arguably what let people like DHH get a platform in the first place.

How many times do I have to give him the benefit of the doubt though?

First it was the “using they in documentation is political ideology” Github issue, then he publicly defended DHH when people called him out for being a white supremacist, he implied tech companies are discriminating against white people with diversity policies, and he tweeted that he hopes young people will carry on Charlie Kirk’s legacy.

If one or two of these things happened in isolation, I could maybe understand giving him the benefit of the doubt as a non-American (for that last one) non-native English speaker. But all of these things taken together? I personally don’t think I can look past that.

All things considered the way they’re approaching the migration is fine enough - they’re only moving specific portions at a time, they’re not stopping C++ development, and they’re making sure it doesn’t introduce regressions. Adopting a memory-safe language for something like a browser makes sense because it completely eliminates that class of vulnerabilities.

The problem is the way they’re approaching the code itself. From their wording, it sounds like they’re relying on AI heavily for both writing and reviewing the code. Rust has a steeper learning curve than most languages and is very different from C++. They even mention in the blog that their current Rust code looks like C++ code ported over. If they don’t take the time to actually learn Rust before adopting it, it’ll just lead to security logic issues that their AI couldn’t catch because C++ and Rust don’t always behave the same way. And that’s completely ignoring all of the other ethical/technical issues with AI

Ok but the radio station change might cause my car to spontaneously combust so I should make a new car from scratch with my car factory just in case, that way I’ll still have a car.

Never change, NixOS

Presumably companies would be able to argue they aren’t pushing out pollutants with the intention to change the climate

Nah NixOS is a picture of a factory automatically making cars

Presumably just for transparency in case humans down the line went looking through closed PRs and missed the fact that it’s AI.

Xlibre is backed for the most part by the singular maintainer that was still willing to work on X11 who got kicked out for being too toxic and breaking existing code. For what it’s worth, it also explicitly used MAGA language in its README for a while.

Phoenix is intended to allow for support of legacy software/DEs and provide a more modern/maintainable version of X11. It isn’t trying to compete with Wayland, it’s trying to live alongside it for environments that won’t or can’t move to Wayland. It also technically won’t be a complete X11 implementation, as it’s ignoring older portions of the protocol.

Neither option addresses the elephant in the room: The X11 protocol is still fundamentally broken in a lot of aspects. Multi-monitor support, especially when monitors aren’t the same resolution, refresh rate, or physical size, is broken at a fundamental level. It will never work even as well as Windows, which is already an incredibly low bar to clear.

Wayland is slow moving, sure, but it is a much more stable base to work with than Xorg ever was. From a security, modularity, and extensibility standpoint, Wayland is a lot better. There is a reason most of the Xorg team developed a completely new protocol instead of just reimplementing X11 themselves.

It can be hit or miss, really depends on the bank. I’m in the US and mine worked fine after I enabled a compatibility setting in the app list, but that’s kind of anecdotal. I think there is a community compatibility list somewhere of banking apps that work/don’t work on GrapheneOS.

If you were able to install Bazzite then installing graphene shouldn’t be any harder than that. It has a web-based installer that was pretty easy to use as long as you follow the instructions.

The pixel 8 will be supported through the end of 2030 (graphene support follows the same timeline as Google because of firmware-level updates that are still needed from them) so you could still get a lot of use out of it.

GrapheneOS my beloved

Not just designed, lawnchair is a fork of the AOSP launcher which is why they look so similar. It’s also partially why they have a comparatively slow development cycle, because they spend a lot of effort rebasing whenever AOSP’s launcher has significant changes.

Lawnchair doesn’t have a paid version, it’s open source

It’s a kernel compile parameter but most Linux distros have it turned off by default 😔

The only time I’ve ever seen it turned on was on my raspberry pi

They can also use live location data in an emergency situation,also using a court ordered subpoena.

What qualifies as an “emergency situation”? I imagine that definition could be stretched pretty thinly

If you want to be technical about it, there could (and probably are given OnePlus’s security history) still be unpatched firmware bugs that will never get patched because OnePlus and Qualcomm have stopped supporting their CPUs which are that old.

Not saying anyone should turn their working phones into e-waste, only that you probably shouldn’t treat it like it’s perfectly secure either just because it’s flashed with the newest Android. Be careful with any super sensitive logins like bank accounts and government sites.