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.
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.
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.
Poor comprehension of the law. LLC in the vast majority of the western world means limited liability, not absolute immunity. Owners are 100% responsible for the actions of their companies, but their liability is limited when other members of the company act without their knowledge or in bad faith, or damages are unintentional. If the damage was intentional and the actions were sanctioned and approved by ownership or leadership they are absolutely liable for the legal repercussions. Liability is limited also for multiple owners, a hedge fund cannot be held responsible for the action of a company they only own 5% of and has an indirect influence on the actions of leadership. The really important element here is that Musk is being identified as acting as primary agent, not just Twitter, and using assets and resources from his other companies. Thus, it’s not Twitter acting, it’s Musk who is acting, and then fines can be on all of his capital holdings, not just Twitter. This nuance of law is exactly according to the laws in place in the EU.
Sorry, I was not replying to you (not an insult). I assume you are interacting from Mastodon from the format of the comment, and getting pinged on replies to other comments (?). I mean, you do you, absolutely not going to diss people who want absolute control over their system. But immutable distros are fundamentally an entirely philosophically different approach from how traditional Linux distros have been packaged and managed in the past. That said, I didn’t make the installers, I’m just reporting what has been my recent experience toying with immutable distros. The whole point is to automate as much as possible of the deployment and management of an OS, and do the least amount of tedious manual troubleshooting. If you don’t like that, all the other distros are still there, they haven’t gone anywhere. The current recommendation for Fedora Atomic based distros is to use specialized tools like Universal Blue that allows the user absolute freedom to deterministically configure a Fedora install that results in an immutable OS. And the installer is actually pretty flexible to let you choose how you want the disks laid out. But, the idea is that you should let the installer do its job, that’s for what it was made. If you want to do everything by hand just use Arch, that’s what Arch is for.
You should let the installer do the partitioning. Silverblue and immutable systems are nitpicky about it. Specially if luks is involved. The whole point is that you shouldn’t meddle with the system at a low level at all.
Did you reformat the disk before installing? I’ve seen similar fails when the disk is still encrypted. The installer can’t get a hold of a previously encrypted disk. If there’s no valuable data in the disk, load up a live distro run gparted and nuke the disk blank and pristine again, as gparted doesn’t care about encryption. Then try the installer again.
I didn’t have much choice. Where I am imports are heavily restricted and the market is not very keen on alternatives anyways. I already had a slim number of options to begin with. Importing a linux first brand, a used thinkpad or a fancy framework as is the fashion on the first world would’ve cost me about three times what I paid for the model I got, and I already got it with a bit of overcharge. Just on port fees, taxes, etc. Trust me, I did my research and this was the best performance and compatibility with linux for money I could get where I am. Windows 11 license cost is not even a factor, we just don’t get a choice to not factor it in the price.
So, I just bought a new laptop. It came with Windows 11. But anyways, I’m writing this comment from a freshly installed Bazzite Linux OS.
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.