Switching from Windows 11 to Linux for Web Development + Gaming — Bazzite or Nobara?

[brfignoni]

Hello everyone,

I am planning to migrate from Windows 11 to Linux, so I would still consider myself a new Linux user. The main reasons for switching are that I have heard Linux is more secure, lighter on system resources, faster, and generally a better environment for development work.

I am a front-end web developer, and I am very interested in things like Docker, local AI tools, terminal workflows, self-hosting, and development environments in general. At the same time, gaming is also important to me. I use Steam heavily, so good gaming compatibility is something I care about a lot.

After researching for a while, the two distros that seem most interesting to me are Bazzite and Nobara.

From what I understand:

• Bazzite seems more “it just works” and focused on a smooth out-of-the-box gaming experience.
• Nobara seems a bit more configurable and flexible for advanced users and developers.

My impression is that Nobara may fit my interests better as a web developer, especially because I want to learn Linux more deeply and work comfortably with containers, development tools, AI-related software, and terminal-based workflows.

So I would like to ask experienced Linux users:

• Is Nobara actually a good distro for web development long term?
• How stable and reliable is it for daily development work?
• How good is Docker support and developer tooling on Nobara?
• Would Bazzite still be the better choice if I also care about gaming stability?
• Are there other distros I should seriously consider for a balance between development and gaming?

I would really appreciate advice from people who use Linux both for development and gaming.

Thanks.

 

[AlphaObeisance]

Quite literally either one of those will do whatever you want. They're both just customized Fedora distributions. Nobara is lead by GloriousEggroll, pretty much "the' forefront of custom proton development. So if gaming is a big deal to you, I'd say go that route.

That said. Steam is supported on literally everything.

Try not to get sucked in by the Tribalism Vampires. "Which distro is best" is probably the worst question you could ask because Linux is notorious for having an army of "experts" chomping at the bit to tell you how awesome their distribution is and why; while simultaneously avoiding telling you that literally any distribution can do the same exact thing.

It boils down to "bleeding edge" and "stability", or so they say. Since both Bazzite and Nobara are both founded on Fedora, they're both going to be pretty cutting edge, but it's like comparing brother and sister; literally, because no matter how you look at it Fedora's still the daddy.

My advise, you'll get a more rewarding experience looking into what desktop environment you'd prefer over which distribution to use. As a desktop environment is going to give you more drastic changes than distribution; especially in your prospective choices.

If you really want to learn Linux. Just install Fedora and look into what tools you'd want to customize your experience. Ensure you have the proper CPU/GPU ucode and drivers installed to support your system and go ham.

Enjoy. Welcome to Linux. God Speed. Carry garlic and silver stakes.

EDIT: I should note that Bazzite is immutable, which personally I would consider a negative for a newcomer due to the restrictive nature of an immutable system. I would find this to be the sole reason I'd avoid it personally for development reasons. But that's just me.

 

[MikeWalsh]

@brfignoni :-

Absolutely. @AlphaObeisance has said it all, really.

Especially the bit about the tribalism "vampires"..!

(I'm probably at t'other end of the scale. I use 'Puppy' Linux exclusively; a small, featherweight "hobbyist" distro - running as root! - which lets you pull all kinds of crazy stunts. Most folks would be scared of bricking their systems if they tried some of the stuff we take for granted..!)

I will NOT recommend Puppy to beginners....and this is NOT 'elitism' on my part, just being 'pragmatic'. She does many things sufficiently differently to mainstream distros, with the result that the majority of tutorials simply don't work properly. Even Linux veterans get confused by her.....so you can imagine how noobs would get on.

I always say to get used to the mainstream first. Come to Puppy in your own good time, when you're beginning to feel comfortable with the whole process. If you don't like what you find, you can return to the mainstream & carry on as before; no harm, no foul.

~~~~~~~~~~~~~~~~~~~~​

In all honesty, it's impossible to say to anyone, with any degree of certainty, that THIS - or THAT - distro WILL work for your use-case. Linux distros cover the gamut of different needs; you've already done some research, and narrowed-down the distros you think would do what you want. That's great, and shows you're already more "committed" than many (who are simply curious, and are basically 'window-shopping' at the end of the day).

Download a handful of the distros you've focused on, and try them out in "Live" mode (something all Linux distros will let you do, with very few exceptions). Nobody can make this decision FOR you; it has to be YOUR choice.....and yours alone. You're the one who's going to have to live with it, after all.

All distros have their fanbois; we, too, have our fair share of "distro evangelists" who will do their level best to convince you that only THEIR distro of choice is "the answer". Listen by all means.....but only you can eventually decide if what you have is working for you.

We can only advise.


Mike.

 

[f33dm3bits]

Also have a look at PikaOS while you're at it.

What Makes PikaOS Different?

wiki.pika-os.com

 

[Bitwor1d]

I always say to get used to the mainstream first. Come to Puppy in your own good time

So there are even more advanced, down to the machine level, linux distros out there?

I thought it was enough with just taking debian for example and modifying the kernel to your needs, play with it or see how the car works under the hood.

Interesting...

 

[Rocketing-warp9]

Like Shrek and Unions, Linux itself has many Layers. There's Debian and others with regular GUIs for us base users, then there is WMs that are a layer lower than that, then just Straight CLI, Then LFS.

In a distro-like level, Goes like this. Ubuntu-Debian,Fedora,Manjaro,Puppy,Arch,Gentoo,LFS.
Each are different layers geared to different users and use cases. All are quite interesting.
You can "Peel back" different layers and eventually you will technically always end up with something like Gentoo/LFS.

 

[KGIII]

Unions

LOL Your typo cracked me up.

 

[Rocketing-warp9]

I can't spell to save my life sometimes LOL

 

[gvisoc]

Bazzite and Nobara

The fundamental difference is that Bazzite is atomic, and Nobara is not.

An atomic distribution is based on how the system's paths and files are managed between reboots. In an atomic system, the system's directories and files are read-only, and the changes over them, that are fundamentally upgrades, are only applied at reboot. When that happens, the applied upgrades and changes are a differential on top of the previous system that can be rolled back with a very simple operation.

They are essentially more resilient and easier to recover after a failed or breaking change.

This imposes differences in the day to day usage if you're going to get anywhere beyond the desktop environment and UI applications. Without entering in too many details:

• Package management is different. In Nobara, you can install, uninstall and update packages with a tool called dnf. You can write anything anywhere using sudo. In Bazzite, you layer packages on top of the system using rpm-ostree. You can't modify some files as easy as you could in Nobara.
• To work in the terminal and with CLI tools, Bazzite forces a workflow based on desktop containers through distrobox, which has dnf (or apt, or pacman, depending on the base image of your distro box).
• In Nobara, using distrobox is possible, good, but optional, as you can modify the system's files and install stuff in the bare system with dnf.
• Both systems work well with Flatpaks, but in Bazzite most --if not all-- user applications with UI are Flatpaks. Flatpaks are the recommended / supported way to install UI applications in Bazzite and it may as well be a good recommendation for Nobara.
• In Nobara you can install UI applications with dnf and in Bazzite you'd have to layer them with rpm-ostree. The downside of this is that, the more layered packages you have, the slower the upgrade operations are in Bazzite.

I'd suggest you to read about the above concepts and tools if you haven't, and maybe give them a crack in a VM to experiment the differences yourself before nuking any drive.

So yeah, they are similar until you open the hood.

 

[MikeWalsh]

@gvisoc :-

A very good overview. Thanks!

I have to confess, I'm curious though. Through long usage, I understand Puppy's mechanism inside out, and in many ways, she's as close to being "atomic" as these modern mainstream distros are.

I'm wondering if you know how the "persistence" is handled.

Traditionally, Puppy always used the AUFS 'layering' system, which permits the layering of the "save-file" ( or -folder ) on top of the base installation.....in such a way that, insofar as the user is concerned, the OS - as presented - is a homegenous instance, as fully integrated as any mainstream distro is.

In recent years, we've been slowly transitioning over to the in-kernel 'overlayfs' module, due to the maintainer of AUFS - an elderly Japanese guy, one J.R. Okajima - encountering increasing difficulty in 'patching' the AUFS code to integrate it successfully with more modern kernels.

~~~~~~~~~~~~~~~~~~~​

Does Bazzite use some kind of 'layering' in order to achieve persistence? And if so, can it voluntarily turn that persistence "on" or "off", in the way that Puppy has always been able to? This enables the same installed instance of Puppy to run as either the fully-fleshed variant the user has taken time to set-up/customise to their liking, or, via a simple boot-time edit, to run as a "Live" vanilla install instead.....if it should be required for, say, trouble-shooting.

This does away with the need to run a separate "Live' instance alongside the instance with 'problems', or 'issues', since the save-file/folder is always accessible from ANY running Puppy, even if the two don't belong together.

(Puppy can even run its base installation from one drive, and its "save" from a second, completely separate drive IF the user wishes.....so long as the appropriate parameters are added to the boot-loader's kernel line.)

I've looked high & low for some kind of explanation as to how these "atomic" distros do what they do. Haven't had much luck so far...

Does anybody else know?


Mike.

 

[AlphaObeisance]

So yeah, they are similar until you open the hood.

Mhm. It's incredibly important they be capable of reading documentation as well, regardless of distribution; or whether they think they can conclude it's intent without reading the full context.

EDIT: I should note that Bazzite is immutable, which personally I would consider a negative for a newcomer due to the restrictive nature of an immutable system. I would find this to be the sole reason I'd avoid it personally for development reasons. But that's just me.

Maybe they should just consider NixOS.

 

[gvisoc]

@MikeWalsh there is a lot of documentation in the corresponding Fedora projects, as they are the ones ultimately behind all the distributions that use bootc and rpm-ostree.

The idea is that these installations work pretty much like containers, where the image is immutable between deployments, and then the container instance stores the state in an filesystem overlayed on it. If you think of filesystems that allow you to define an arbitrary number of volumes over a single partition, each one of them with their own behaviour (such as btrfs to name one) and dynamic space allocation, you can guess how this could be done. For example, any fedora installation define "/" and "/home" as separate volumes over the same partition, and both of them have a maximum size of the whole partition, making the partitioning a lot more dynamic.

In practice they have packed all those mechanisms on a set of tools like composefs (see: https://github.com/composefs/composefs) that abstract all those low level operations.

All these concepts and distributions often refer to "bootable containers", as they behave like containers extended to have the kernel and the hardware modules shipped within.

See also: https://bootc.dev/bootc/filesystem.html

 

[MikeWalsh]

@gvisoc :-

Uh-huh. Yah, sounds about like what I expected, IIH.

If you think of filesystems that allow you to define an arbitrary number of volumes over a single partition, each one of them with their own behaviour (such as btrfs to name one) and dynamic space allocation, you can guess how this could be done.

This is, to all intents & purposes precisely what we do in Puppy. My entire "kennels" - all twelve of them! - live on a single partition. This one fact alone throws no end of veterans out, 'cos they're so used to 'full' installs; one partition, one OS.

Puppy's in-house bootloader - formerly a modified Grub4DOS, latterly a modified GRUB2 - is altered to allow searching TWO layers deep in order to find a bootable kernel. And the business of multiple OSs on one partition works because each Puppy 'install' - each a self-contained 'frugal', in its own uniquely-named directory - comprises a handful of highly-compressed read-only 'archive' files, along with with a specially-modified SFS file that contains everything which makes up the current 'state.

These never exist as a recognisable file-system until Puppy is up-and-running.....everything being decompressed into a virtual file-system in RAM, and merged via the magic of a 'layering'-type file-system into a homogenous whole.....which any average user will instantly be familiar with by the time it reaches a working desktop.

Every Puppy 'frugal' - in its own directory - is also totally self-contained, including kernel, modules in a separate SFS, firmware in another, etc, etc. It all makes for a highly-flexible & easily-modifiable system with great ease of access.....even for the average user.

I keep poking my nose outside the kennels from time to time, simply to keep in touch with what's going on.....and you know what? Perhaps I've become jaded over the last nearly fifteen years, because I'm honestly not that impressed with the current crop of mainstream distros. Don't get me wrong; all credit to their developers for the huge amounts of hard work that's gone into making such fantastic strides in the realms of user-friendliness & general ease of use, but when I do raise my head above the parapet I find I miss Puppy's overall flexibility, and ability to throw together "unusual", custom set-ups literally at the drop of a hat!

Yup, "our Pup" HAS spoiled me.....that's for SURE.


Mike.