Linux desktop will, most likely, fail for:
Developers and sysadmins, because not everyone is using Docker and Github actions to deploy applications to some proprietary cloud solution. Finding a properly working FTP/SFTP/FTPS desktop client (similar WinSCP or Cyberduck) is an impossible task as the ones that exist fail even at basic tasks like dragging and dropping a file.
Linux desktop is great, I love it but I don’t sugar coat it nor I’m delusional like most posting about it.
It all comes down to a question of how much time (days? months?) you want to spend fixing things on Linux that simply work out of the box under Windows for a minimal fee. Buy a Windows license and spend the time you would’ve spent dealing with Linux issues doing your actual job and you’ll, most likely, get a better ROI.
Guess what happens whenever people popularize immutable distros as the next hype in tech that will make everything better? You get yourself into a totally unreasonable and avoidable ecosystem just because those systems won’t cut it for most use cases… same that happened with Docker/Kubernetes.
I’ve been saying it for year and nobody cares: nowadays those companies are all about re-creating and reconfiguring the way people develop software so everyone will be hostage of their platforms. We see this in everything now Docker/DockerHub/Kubernetes and GitHub actions were the first sign of this cancer. We now have a generation of developers that doesn’t understand the basic of their tech stack, about networking, about DNS, about how to deploy a simple thing into a server that doesn’t use some Docker BS or isn’t a 3rd party cloud xyz deploy-from-github service.
The latest endeavor in making everyone’s hostage is the new Linux immutable distribution trend. Immutable distros are all about making thing that were easy into complex, “locked down”, “inflexible”, bullshit to justify jobs and payed tech stacks and a soon to be released property solution.
We had Ansible, containers, ZFS and BTRFS that provided all the required immutability needed already but someone decided that is is time to transform proven development techniques in the hopes of eventually selling some orchestration and/or other proprietary repository / platform / BS like Docker / Kubernetes does.
“Oh but there are truly open-source immutable distros” … true, but this hype is much like Docker and it will invariably and inevitably lead people down a path that will then require some proprietary solution or dependency somewhere that is only required because the “new” technology itself alone doesn’t deliver as others did in the past.
As with CentOS’s fiasco or Docker it doesn’t really matter if there are truly open-source and open ecosystems of immutable distributions because in the end people/companies will pick the proprietary / closed option just because “it’s easier to use” or some other specific thing that will be good on the short term and very bad on the long term. This happened with CentOS vs Debian is currently unfolding with Docker vs LXC/RKT and will happen with Ubuntu vs Debian for all those who moved from CentOS to Ubuntu.
Those popularizing immutable distributions clearly haven’t had any experience with it before the current hype. Let me tell you something, immutable systems aren’t a new thing we already had it with MIPS devices (mostly routers and IOTs) and people have been moving to ARM and mutable solutions because it’s better, easier and more reliable.
There is always some solutionizm in tech, but I’m interested in containerzation as a solution to problems I’ve had with configure drift building up on my systems and make it easier to share and work with the community.
The immutable desktop work to me is specifically working on bridging the gap between the UX of a local admin (you know wanting custom configuration and fast reaction to user input) and the industrial expectations of being able to test and track every change and reduce the number of different pieces you need to operate a system.
Hopefully we can lose some of the industries bad habits though. Like “relying on this proprietary piece is ok because we can move faster” or making other excuses as if you are going to have to explain to your boss why some metric looks bad instead of just trying to make the best system or solution we can.
https://tadeubento.com/2023/linux-desktop-a-collective-delusion/
Also, immutable distributions are a scam:
Guess what happens whenever people popularize immutable distros as the next hype in tech that will make everything better? You get yourself into a totally unreasonable and avoidable ecosystem just because those systems won’t cut it for most use cases… same that happened with Docker/Kubernetes.
I’ve been saying it for year and nobody cares: nowadays those companies are all about re-creating and reconfiguring the way people develop software so everyone will be hostage of their platforms. We see this in everything now Docker/DockerHub/Kubernetes and GitHub actions were the first sign of this cancer. We now have a generation of developers that doesn’t understand the basic of their tech stack, about networking, about DNS, about how to deploy a simple thing into a server that doesn’t use some Docker BS or isn’t a 3rd party cloud xyz deploy-from-github service.
The latest endeavor in making everyone’s hostage is the new Linux immutable distribution trend. Immutable distros are all about making thing that were easy into complex, “locked down”, “inflexible”, bullshit to justify jobs and payed tech stacks and a soon to be released property solution.
We had Ansible, containers, ZFS and BTRFS that provided all the required immutability needed already but someone decided that is is time to transform proven development techniques in the hopes of eventually selling some orchestration and/or other proprietary repository / platform / BS like Docker / Kubernetes does.
“Oh but there are truly open-source immutable distros” … true, but this hype is much like Docker and it will invariably and inevitably lead people down a path that will then require some proprietary solution or dependency somewhere that is only required because the “new” technology itself alone doesn’t deliver as others did in the past.
As with CentOS’s fiasco or Docker it doesn’t really matter if there are truly open-source and open ecosystems of immutable distributions because in the end people/companies will pick the proprietary / closed option just because “it’s easier to use” or some other specific thing that will be good on the short term and very bad on the long term. This happened with CentOS vs Debian is currently unfolding with Docker vs LXC/RKT and will happen with Ubuntu vs Debian for all those who moved from CentOS to Ubuntu.
Those popularizing immutable distributions clearly haven’t had any experience with it before the current hype. Let me tell you something, immutable systems aren’t a new thing we already had it with MIPS devices (mostly routers and IOTs) and people have been moving to ARM and mutable solutions because it’s better, easier and more reliable.
Let people enjoy things.
What if I enjoy ruining other people’s fun?
There is always some solutionizm in tech, but I’m interested in containerzation as a solution to problems I’ve had with configure drift building up on my systems and make it easier to share and work with the community.
The immutable desktop work to me is specifically working on bridging the gap between the UX of a local admin (you know wanting custom configuration and fast reaction to user input) and the industrial expectations of being able to test and track every change and reduce the number of different pieces you need to operate a system.
Hopefully we can lose some of the industries bad habits though. Like “relying on this proprietary piece is ok because we can move faster” or making other excuses as if you are going to have to explain to your boss why some metric looks bad instead of just trying to make the best system or solution we can.
I care!