I can’t express how much I disagree with you and further I can not fucking stand flatpacks and the like. Unless I’m running a server, I don’t want that crap on my box at all.
Why would you want flatpak on a server, server feels like ideal for dynamic dependencies as you have some highly used, static build (Debian 13 or Ubuntu LTS) where problems can be easily tested and fixes distributed out. The dependencies don’t change too much aswell as the usecase for the server stays static. Security features can then be patched in when needed. Desktop usecase all people want is an up to date latest app that works, security rarely matters, and the dependency graph is highly volatile as people constantly update and add new software
So keep the different server processes somewhat isolated without going full VM. If I was admining production boxes for a company, I’d go with VMs. I’m talking about home servers running a couple services, and about desktops at home. Being retired, I haven’t had to really do real sysadmin work for years.
I haven’t had any issues, that I can think of at least, updating my desktop install which is going on about 10 years now. I’ve not been stuck in some type of dependency hell for even longer than that. To each their own, if they work for you, great. I can’t stand the extra layer that flatpaks bring to me. Seems like back in the day they would have been really useful…but thinking about past hard drive space, processor speeds, and internet speeds, maybe not.
Are you confusing flatpaks and other containerization solutions like docker? Flatpaks are specifically for UI applications, and that doesn’t make much sense on a server.
I can’t express how much I disagree with you and further I can not fucking stand flatpacks and the like. Unless I’m running a server, I don’t want that crap on my box at all.
Why would you want flatpak on a server, server feels like ideal for dynamic dependencies as you have some highly used, static build (Debian 13 or Ubuntu LTS) where problems can be easily tested and fixes distributed out. The dependencies don’t change too much aswell as the usecase for the server stays static. Security features can then be patched in when needed. Desktop usecase all people want is an up to date latest app that works, security rarely matters, and the dependency graph is highly volatile as people constantly update and add new software
So keep the different server processes somewhat isolated without going full VM. If I was admining production boxes for a company, I’d go with VMs. I’m talking about home servers running a couple services, and about desktops at home. Being retired, I haven’t had to really do real sysadmin work for years.
I haven’t had any issues, that I can think of at least, updating my desktop install which is going on about 10 years now. I’ve not been stuck in some type of dependency hell for even longer than that. To each their own, if they work for you, great. I can’t stand the extra layer that flatpaks bring to me. Seems like back in the day they would have been really useful…but thinking about past hard drive space, processor speeds, and internet speeds, maybe not.
Are you confusing flatpaks and other containerization solutions like docker? Flatpaks are specifically for UI applications, and that doesn’t make much sense on a server.
Shit, yeah. I’m dumb. I’ve just grouped those together in my mind.