It’s not a flaw. Ostree is a last resort, you should be using containerized software. Layering a package should only be done when strictly necessary and not as the regular way to manage packages. If you need an overtly customized system, you use Nix or universal blue to design your new system declaratively and create your custom image.
Then just install KDE in your Arch install. Or use endeavorOS with KDE, or any other Arch based OS with KDE. Don’t be dismissive of other people’s interests.
Settings live in user space. Software exist in containers like AppImage, Flatpak or Distrobox. If something need deep system integration, they can be layered on top of the system in the user layer. Immutable does NOT mean less control. Just exerting control over the system in a different, usually more systematic, automatic and deterministic way.
your base distro is immutable, then any extra changes go on an additional mutable layer
That is exactly how OsTree and other layering solutions work. Only Nix requires a whole distro rebuild.
There’s KDE Neon already. The whole point of this distribution is the atomic immutable part.
Maybe they’ll fix the sddm custom theming? It’s currently broken on all immutables and doesn’t allow custom themes.
SC is a scam. Of course they’re willing to break the law to keep the money they stole.
Brain damage in general is my hypothesis. Repeated head trauma, toxic substances like drug abuse and heavy metals in general. Anything that damages brain tissue eventually disrupts the ability for rational thought in the mild end to disconnection with reality altogether in the most extreme cases of psychosis.
On Mint, you troubleshoot the wifi antenna following a guide once and then you’re done. On Bazzite you probably just needed to click to change to X11 instead of plain Plasma, on the login screen. I would bet money that you have an Nvidia GPU. Sometimes Nvidia breaks the drivers support on Wayland. They intentionally neglect it in order to keep your kind of mentality around.
On Windows, MS is going to eventually fix the workarounds so you can’t update your computer anymore.
How is having to apply workarounds to keep windows working on old machines any different from troubleshooting the occasional linux issue? It’s a rethorical question, the difference is that the workaround on Windows is mandatory while the Linux troubleshoot is nowadays rare and usually related to edge cases.
Some of the workarounds in this article are far more involved and convoluted than what I’ve ever had to do in 15 years of linux. Some are even dangerous for system stability and security. My very recent install of bazzite in a new laptop has been a perfectly out of the box it just works experience. Not even having to open the terminal. 100% friendly GUI without compromising flexibility, power and customizability. Today, suggesting linux with a solid desktop environment like KDE plasma is just foolproof. The end user will be using exactly the same knowledge and habits of Windows, without the harassment machine that is MS now. The change is not learning a new OS, is just switching a few assumptions on how some advanced things work.
If this were done by MS or Apple, who lack any shred of respect left, sure. If it were a material change on how the code works, certainly it would be most concerning. But what happened was blown entirely out of proportion for who Bitwarden has been and how they’ve acted in the past. They are still ethically very solid. And it was an immaterial change in the build tools, that could very well have been neglectful or accidental.
That’s a poor understanding of the situation. Nothing in the licensing changed. The SDK has always been the proprietary business to business secrets management product. The client integrates with and can use that SDK to provide the paid service to businesses. The client and the server side management of password has always been and still is FOSS.
This was apparently an accidental change in the build code (not the client code, just the building scripts) that required the inclusion of the SDK to build the client when actually it has never and doesn’t really need any of that code. It prevented building the client without accepting the SDK license. Which it shouldn’t.
This was fixed and some things will be put in place so it doesn’t happen again. Nothing in the licensing scheme changed, at all. This is not a catastrophic enshittification event. A Dev was just being lazy and forgot to check the dependencies on the build chain before their commit.
Firefox has all those things already (albeit vertical tabs are experimental still). Just without the AI marketing and the built-in identity theft.
Surely the former because at least clowns try to be funny and entertaining.
Oh no, orbit is actually quite hostile. Specially unexpected torque forces from spinning in unplanned ways. And there’s very little but definitely present atmospheric drag. Not so much from the density of the air but from the extremely high speed it’s moving. Then there’s orbital debris. Also extreme and fast changes in temperature from the sun. Not to forget cosmic radiation.
It’s latin. Pause literally means stop in latin.
The SDK was never FOSS, and was never under the GPL. Hence why they can add the text mentioned in the article. You don’t get to change the text of a FOSS license to begin with. It isn’t unheard of for text like this to be part of proprietary software that integrates with and uses FOSS that are under different licenses.
That said, this is concerning, but whether it changes BW’s FOSS state is a matter of legal bickering that has been going on for decades.
SC is a scam. They sell ships for real money that only half work. The game is riddled with bugs, quests don’t complete. Users state is regularly wiped so there’s no point on progressing in it and instead of finishing the game they ask players for much more money to work on tiny niche technical problems that sound super important on presentations but don’t move the needle even a little bit towards a finished game. At best, it is video game history most expensive physics toy. In reality, when you scrutinize their finances executives have pocketed most of the money raised and devs have been paid poor wages and overworked to a constantly moving target. They have never finished a single roadmap item, but they have announced to fanfare at least 5 different development roadmaps that are the very definition of scope creep. Lots of announcements but never a release. Any competent studio would’ve delivered at least three completed games in the same timeframe for that amount of money. They’re an online asset store that sometimes let’s you fiddle with the digital models, not a video game.
Unfriendly reminder, and absolutely unfun fact, that torture’s entire point is to break a person’s will so they’ll say and do anything the torturer wants. So, if you can withstand days or just a few seconds is completely irrelevant. Even if you give up right away before the torture even starts, you’d be tortured anyways, because it’s not about the cognitive and rational surrender, it’s about the visceral subconscious surrender of agency to another’s will. Disregarding all rationality.
Please remember that no one is taking anything away from you. If you don’t like it, you don’t have to use it. Traditional package managing isn’t going away any time soon. You are safe. Others can have their preferred tech, and you don’t have to like it. It’s ok to have different tastes.