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.
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.
We are going to burn the planet to make a shitty chat bot.
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.
You’ve never shared your intimate personal life with anyone? Your fears and woes, and happiness and triumphs? One of the wonderful qualities of deep friendship is the ability to withstand long stretches of being apart and still shine as brigth as the last time you met. I have a couple of people right now who I haven’t seen or talked to in years. But I have the utmost certainty that if I were to pick up the phone and write them “hey, can we talk?” I would get an almost immediate response, despite the timezones. And the conversation would flow as if we just talked yesterday. That, is friendship to me.
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.
Just tried Heliboard, its glide typing support is experimental and requires hacking GApps to extract libraries or download someone’s else glide library from the internet. I guess my threat model remains for the time being.
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 not connected to the internet and doesn’t send or receive any telemetry at all. It’s API is very minimal as well. I fear Gboard to compromise me far more than this app. Keyboards don’t need internet connection.
Openboard with swipe.
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.