I definitely think so. Init was a mess of bash scripts and concurrency and whatnot was a problem. Making a script to start a service was very dependent on the distro, their specific decisions and whatnot. Systemd services and timers make things very easy and they have great tools to manage those. And now it’s basically the same on every distro.

“Youlag” lmao

Well, date time stuff for a system working with timers and scheduling actions might be pretty useful…

I don’t think they are using popularity as a metric. But I think the functionality of it is also very good, so dunno what their gripe is.

So even when you lose you win.

I feel like the glued together collection of scripts was way worse to manage than systemd.

No, UNIX philosophy demands that every single one of those things is one or more separate things and that half of them are poorly or not at all maintained. Just like God intended.

How is this functionality bad?

I’ve felt like systemd has been a breeze compared to the hodgepodge of different stuff that preceded it. Now most distros have it mostly the same way, tools are well documented, things works together. It wasn’t always like that from what I remember

Not that that’s bad when it’s stuff like this

I think this is for setting date oriented timers

Sucks a high hard one if you plan for others to use your services too. If it’s just you it’s not that annoying

How did KDE break your LUKS…? I find that hard to imagine

Also KDE Neon is a test distro (they don’t call it that from what I remember) for those who want to try out newest KDE lol

Should’ve used a systemd timer for this

Yes but that wasn’t the original comment I replied to was about.

I know this doesn’t matter these days but once again that wasn’t what the original comment was about.

I agree, it was just about the size differences. I just think it’s good to bring up since there’s many confused about the flatpak size use. Often people might want to install some small app and they’re hit with gigs of stuff and come off thinking that’s the same for every app, which would be insane of course.

WAIT I just took a deeper look at the link, isn’t that guy just showing the runtimes without the applications using 8.7 GiB?

Yes it’s specifically comparing runtimes. Same for my number, I was calculating how much the runtimes used.

If you allocate 30 GB for / that seems pretty low these days for a desktop system. If you don’t have much space, it’s always best to go with regular repository packages

Here someone had 163 flatpaks and it used 8,7GB in runtimes. So I’m guessing the 30GB number is for whole of /.

I just checked out mine, I have 34 apps and runtimes use 3,1GB

Runtimes are shared in theory but not in practice.

I think three runtimes (newest freedesktop, KDE and GNOME) cover 90% of my flatpaks. Then there’s programs that use some EOL’d runtime and never get updated, which sucks

You should test it out with those 33 installed as flatpak. If you end up with 4.7GB for runtimes, that’s basically nothing these days as far as storage goes for that amount of programs. More you have, more you benefit from shared runtimes. I doubt it’ll be less than AppImages but it’s usually the starting runtime space use that shocks people.

Here someone tested it with 163 flatpaks and the runtimes used 8.7GB. With the top 5 most used runtimes covering 128 of those flatpaks.

https://blogs.gnome.org/wjjt/2021/11/24/on-flatpak-disk-usage-and-deduplication/

I just checked out mine, I have 34 apps and runtimes use 3,1GB

It doesn’t matter if they share if in the end they end up using several times more storage than the appimage equivalent.

Well we are talking about two gigs, after all. Unless you’re using an embedded system, it’s not a much of a concern if you ask me. But it is more, true

If it works for you then it works, no need to switch it up. I guess one other way of doing it would be a persistent install on that USB.

Not a fan of AppImages myself. For an universal format it has surprising amount of issues with different distros, in my experience. And the whole Windows style “go to a website, download the AppImage, if you want to update it, go to the web page again and download it again” is one thing I wanted to get away from. At least they don’t come with install wizards, that clicking through menus thing was a pain.

For one off stuff I run once and never need again, AppImage is alright. But not being built-in with sandboxing, repos, all that stuff, it just seems like a step back.

Then again, loads of apps share that runtime. And if other runtimes have same stuff as that GNOME runtime, the shared parts are on your disk only once. It’s pretty smart in how it works.