Quote:
It's a very unlinuxy (and inefficient and inflexible) way to distribute software.
It's not even an especially new of novel idea. I mean, I struggle to see what's different in principal between say a snap, and an old windows or DOS program that installs all it's gubbins, and maybe a runtime or whatever into its own program directory. I'm not saying there aren't differences, but...
When I started running nextcloud as a snap, of course I was impressed. I'd run owncloud for years and migrated it across boxes and reinstalled it when upgrading distros. then I moved to nextcloud because I'd hit an owncloud error which I couldn't resolve and I was at the limit of free help from the company. Then I found I needed to rebuild the box yet again and the prospect of reinstalling apache or nginx and configuring letsencrypt and all the bollox all over again seemed such a drag, so yes, one command "sudo snap install nextcloud" which did 90% of the work seemed pretty good to me. It has it's irritations, like logs being in a different place and you have to use snap commands to configure things (which I always forget), but I'm not complaining. But I imagine if you're very used to a system managed by apt or rpm etc. then it could be annoying in the extreme.
Back on the topic of systemd, yes, exactly that. I can't see how a layer to manage the launch of things that persist is anything other than a good idea. Then I think, well hang on, so how did stuff work before? Things didn't just fall over or run amok all the time (well yes, some did, but they still do). And when you look, of course there were other solutions. It's just that systemd is sweeping all away. The interesting question is "why is that happening?".
Quote:
As soon as I can run my games on BSD I'll probably hop over.
Or write your own kernel, operating system suite, systemd enquivalent? Call it DinLin, Drew is not linux.He May Be Your Dog But He's Wearing My Collar
|
