It does sound like it could become a solid option for people wanting to ditch Windows and want a simple, easy to use distro that just works out of the box with GUIs for everything they'll ever want to do so they never have to touch the oh ever so intimidating terminal.
post
Well, only the base OS in /usr is immutable; /etc is writable for making system-level config changes, and your entire home folder is of course yours to do what you want with, including installing software into it. So that’s what you do: use Discover to get software, mostly from Flathub at this point in time, but Snap is also technically supported and you can use snap in a terminal window (support in Discover may arrive later).
That’s fine for apps in Flathub and the Snap Store, but what about software not available there? What about CLI tools and development libraries?
Containers offer a modern approach: essentially you download a tiny tiny Linux-based OS into a container, and then you can install whatever that OS’s own package management system provides into the container. KDE Linux ships with support for Distrobox and Toolbx.
It sounds like more work for the user than a single system-wide package manager. And in my experience there are some applications that are not designed for sandboxed installations, where you have to fiddle around with the sandbox settings to get things to work. I've become frustrated by this in the past and ended up going back to system-level, unsandboxed packages. Likewise, managing containers for CLI applications can be great or it can be a pain for similar reasons. Some things are just easiest when fully integrated with the OS, though it brings security and stability risks. So I haven't been won over by immutable distros yet but I'll be interested to see whether KDE Linux can soften some of these hard edges for the user. It sounds like they do want it to be viable for non-experts coming from Windows.
This project sounds pretty cool, I've always liked KDE, run Neon for many years. I'll surely keep an eye open when this comes out of alpha.
As a relatively new Linux user, I picked KDE Neon for my work PC as I figured it made sense to have direct access to up-to-date KDE software. So I'm kind of disconcerted at reading that Neon is considered by KDE to be at the end of its road.
Given that I just did a regular installation, without putting Home on a separate partition or anything like that, what's the most efficient way of backing everything up and moving across to a distro that's more actively maintained?
I really hope they make it so you can very easily customize and then make an installable copy of your system, like MX Linux does.
Currently making one for my mom and dad in MX since they're basically the only ones who have something like that these days, and their Linux installs are too old for them to update anymore.
Shipping them a USB with an installer that's easy to use with the software they'll use already installed, and Librewolf already configured, would make this awesome.
I don't interact with either of following systems KDE Linux, atomic fedora and opensuse (aeon). What is the difference between them? How can I choose between them?
I used a fedora distrobox for a long time. I couldn't figure out how to upgrade many times. Now, I use aeon with a rolling opensuse distrobox. And I don't have to think about upgrading again. I am not too sure why I didn't think of that before (probably because I didn't care too much).
Note that Homebrew packages are not segregated, so they can override system libraries and present problems. This should be considered an experts’ tool.
To me as an end user it translates to: don't touch brew. what about nix home manager? Is nix as dangerous as brew?
There’s no package manager.
I'm confused. It's based on arch but not really? Is it arch based or not? Does it use any arch package manager? The post raises a number of new questions
I'm confused. It's based on arch but not really? Is it arch based or not? Does it use any arch package manager? The post raises a number of new questions
The answers to that seem pretty obvious to me: yes, it is based on arch. No, it does not come with a package manager. Presumably, they use Arch packaging tools and package definitions behind the scenes in some way, but the end result is a premade immutable system image.
It’s as easy as pie too; they show up right there on the boot menu:
I really don't understand why people have this little awareness of usability. Show the freaking date normally! At least add hyphens.
We tried Dolphin and Konsole as Flatpaks for a while, but the user experience was just terrible.
Yeah I'm fairly sympathetic to Flatpak. It's way closer to how software should be installed by users. But I have yet to actually use it successfully. Is it really ready?
I really don’t understand why people have this little awareness of usability.
It's an alpha release.
Is it really ready?
It's an alpha release.
It’s an alpha release.
You really think they're going to revisit this? That's not really how software development works.
It’s an alpha release.
I was talking about Flatpak.
You really think they’re going to revisit this?
I reserve my judgement until a final release is made.
That’s not really how software development works.
How does it work, then? Have you filed a bug report?
How does it work, then?
I'm assuming that's a genuine question... Normally when people develop a feature they do it once and then it's "done" and any changes to that feature have to go through the whole feature request -> it's low priority -> wait 10 years cycle before they actually happen.
Essentially, you have to do it right first time or it might never be fixed.
Just to note, I disagree entirely. Even in commercial development, it's the core premise of agile development to ship features early and continuously integrate feedback. Granted, lots of companies claim to do agile without actually doing it, but it's at least not a law of nature what you're describing.
But with this not being commercial development either way, I really don't feel like you can make any predictions. If the volunteer that implemented this sees your bug report, they could decide to drop everything else and fix that, because they get to pick their own priorities. They might have the solution in their head right away and it doesn't take them long at all to implement. Or someone new to the project might decide this sounds like a good issue to get started with.
Normally when people develop a feature they do it once and then it’s “done”
The feature (boot manager) was not developed by KDE. They rely in systemd components which are all in active development.
So did you file a bug report or are you just being negative in a forum the developers will probably never read?
Right but presumably they chose the names?
So did you file a bug report
It's not a requirement to file a bug report before you comment on anything. Don't be silly.
Right but presumably they chose the names?
I don't know.
It’s not a requirement to file a bug report before you comment on anything. Don’t be silly.
It's not a requirement but if anything is silly it's acting as if an alpha version is the final release and complaining in a random forum would change anything.
complaining in a random forum would change anything.
What gave you the impression that I thought it would?
What gave you the impression that I thought it would?
What gave the completely irrational impression that filing a bug report before commenting was a requirement?
Oh my god, be more insufferable.
It's an alpha release and you're condemning them to death because of a naming convention.
YYYYMMDDHHmm is probably one of the most normal date-time formats, only slightly behind current ISO 8601. But adding hyphens for the extended format would definitely make it more readable.
YYYYMMDDHHmm is probably one of the most normal date-time formats
No, it absolutely isn't outside the tech sphere
It's really not unless you're a techie who's used to naming files in away that promotes better sorting.
The date format this uses should match with the one you have set in your system, which for most people will be DD/MM/YYYY or MM/DD/YYYY in the US. Because that's what the user is used to seeing.
If you think most people are used to seeing YYMMDDhhmmss then you are in a very tiny and very incorrect bubble lol
Booting to a black screen with white text, while functional, really detracts from the more professional experiences that can be had elsewhere. I know the theming support is severely lacking in systemd-boot though (which I believe this is)
Btw, it uses Arch!
all 8 comments