The main difference to your examples is that an “immutable OS” is in fact mutable, while none of your examples describe themselves with an adjective that is contradicting with their function/inner workings.

Flatpak is a pretty good name, because it makes software flat in the sense that it avoids having a (tall) dependency tree.

I print from my phone just fine

Ah yes, the immutable OS, except for all of the various mutable parts.

We should totally not call it anything less confusing.

How could you install anything or change any setting if it “doesn’t change” ?

How could you install anything or change any setting if it was truly immutable?

Immutable OS makes sense in certain scenarios, but not in home computing.

Nice!

If this is a HDD you could recover it.

If SSD - no.

https://lemmy.world/post/20491286

I use borgbackup with borgmatic.

Backing it up to a local hdd and to a hetzter storage box.

Since you say

change the path the .wav audio file

fyi, the sys BAT paths are also different sometimes per computer. Just in case it doesn’t work for somebody else or for you on a different laptop.

Just fyi

a storage controller on an USB stick also has programmed “Gb” for addressing the flash storage. For example if you want to remove one of the flash chips, you could be asking how to reprogram the controller to use only half of it’s initial capacity. Thats what I was confused about.

But you actually meant Gb/s.

What kind of controller and what kind of Gb are you talking about?

Storage controller for USB sticks?

Or gaming controller with an advertised Gb/s USB bandwidth?

Depends on their specific needs, so they should probably jump into some Linux community and ask for themselves.

My anecdotal evidence includes vastly different experiences.

I have a friend who hates Linux desktop and exclusively uses it for running dev related stuff via WSL.

Another who uses Linux desktop primarely, but dualboots Windows for certain games.

And I am on Linux single boot and rarely use KVM (without GPU) for running my CNC or other software.

Minisforum V3 is 12” and less than 1kg.

But it is not quite a laptop, expensive and very powerful - not sure if that suits you.

Linux wise, most of the stuff works (sleep, power profiles, volume buttons, fingerprint reader, face recognition, pen, touchscreen). Things that don’t work are automatic rotate/accelerometer.

I’m super happy with it, running arch, doing development and using VMs

Let me be more concrete then. What I am used to is the following:

• Open the relevant Jetbrains IDE
• Click on new project
• Find the correct template (e.g. Spring Boot Web Starter) and follow the wizard. (Alternatively the steps before can be replaced with cloning a repo and opening it with my IDE)
• I can click “Play” to start the app
• I can click “Debug” to debug the app
• Bonus: when doing Android or Web development, I can create the GUI by drag&dropping building blocks into a preview (contrary to manually typing out textfiles that describe the layout)

Every step is a button click or a entry field in a dialog. These steps also work on every major distro. And I wish for a similar experience when developing KDE Plasma.

For completeness, I will try to do the same dev things and list the steps for KDE Plasma development later (in about 8h).

Very nice.

I’m very excited, because in the past I have bounced off KDE development. Coming from a java and web background, the tooling and dev environment was just mindboggling.

Install literally every package from the repo, then you can experience breaking OS every day.

The most annoying ones for me personally, in no particular order:

1. https://bugs.kde.org/show_bug.cgi?id=491230
2. https://bugs.kde.org/show_bug.cgi?id=483503
3. https://bugs.kde.org/show_bug.cgi?id=488060
4. https://bugs.kde.org/show_bug.cgi?id=482953
5. https://bugs.kde.org/show_bug.cgi?id=490055
6. https://bugs.kde.org/show_bug.cgi?id=477951
7. https://bugs.kde.org/show_bug.cgi?id=479391
8. https://bugs.kde.org/show_bug.cgi?id=482953

tldr: nothing works - sorry for being bitter

I have reported and/or commented on existing issues when plasma 6.0.0 rolled out on arch and there has been no work on them as far as I can see.

I even asked in the matrix dev rooms.

They were not even triaged. So some describe the same issue multiple times. Check the ones which had activity in 2024:

https://bugs.kde.org/buglist.cgi?component=rules&order=changeddate DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&product=kwin&query_format=advanced&resolution=---

I just hope they fix window rules