I don't get it. What's the spirit of ubuntu? Is the underlying OS based on ubuntu instead of fedora?
What's the actual difference to fedora silverblue?
Half the answer to "why did you make your own linux?" is that it's awesome being able to revert back to the original fedora OS.
Because it follows a cloud-native approach, the end user has the flexibility to rebase back to the stock Fedora or any Universal Blue image. It's more like having someone install, configure, and maintain a polished Fedora setup for you.
And the other half doesn't provide any info either
Bluefin utilizes Fedora's OCI features to compose and build an OS image. This process is overseen by a well-structured community that is committed to automation and sustainability. The end result is akin to a configuration management tool like Ansible or Salt, but without the typical challenges associated with maintaining a custom distribution.
I think it boils down to: "because we can". "We can automatically build our own setup on github and that's what we do"
Installing tailscale, zsh, fish, vscode, extension manager, codecs, etc. out of the box isn't enough for a new distro. Especially because you break the signing of fedora by doing so.
I checked the github page you link and can find no differences listed, just three bullet points that appear to have be written by a PR team. You say an Ubuntu Desktop experience melded with Fedora Silverblue. Don't you mean GNOME? Ubuntu isn't a desktop environment, it's a Linux distro. GNOME is the desktop environment. That seems like an embarassing blunder in your copy when you claim to be building a distro for "serious" developers.
If it weren't open source, I'd think this was a scam. Weird choice.
This is the umpteenth time Iâve come across this project but I just donât get what theyâre going for here.
These are just custom images, are they not?
If I wanted Ubuntu Iâd use Ubuntu. If I wanted Fedora Iâd use Fedora. Maybe Iâm not getting it but I wonder how big of a population thatâs out there that wants some Ubuntu mixed in with a touch of Fedora and some buzzword salad thrown into the mix.
The base OS is a known unchanging set of bits. Squirt this datastream onto a storage volume and boot to it and you have a known-working system. Then you can futz around with all the self-contained packaged apps you want, and no worries about weird interactions fucking over your whole system.
Immutable, adjective: Unchanging over time or unable to be changed.
From the article: "We want a reliable desktop experience that runs everything, but weâre too lazy to maintain anything. So we automated the entire delivery pipeline in GitHub."
So, in other words... "Please don't ever update your system or everything will break"
It means the core OS is isolated from all the functionality in a way that allows you to modularly add all the functionality on top of it in a reproducible, robust way.
In theory. I haven't actually dug into any of them personally.
"Cloud native" technology is double speak for your shit is running on other people's computers who will be tracking your use and selling it to pay for server upkeep and also maybe profit?
In this case it's referring to the fact that the OS is built upon the same containerization technology used on cloud platforms such as Kubernetes. As a marketing tool it's a bit buzzwordy, but it's not about running the core OS components outside of the physical machine here.
Both are incredibly stupid attempts to convince people they need something they don't.
You all should look into a 'blue ocean' business strategy. Lots of shitty businessmen are constantly trying to push 'new' things and have a vested interest in convincing laymen of their necessity.
Needs are born from solving problems, not making them.
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.