LeFantome

Honestly a lot of it is just momentum and familiarity although I also think US vs Europe is a factor. Linux was popular in North America first and Red Hat was one of the most successful distros early on. The fact that SUSE uses the Red Hat package manager reflects this. Fedora is backed by Red Hat, the de facto standard Enterprise Linux.

Both have their fans though and trying to argue that one is better than the other would be a war of preferences. Many people believe that Tumbleweed is the best rolling distro.

If you do not want your distro to force changes down your throat like Microsoft, maybe avoid Ubuntu.

“Stability” on Linux means two things. “Stable” distros like Debian or RHEL change their software infrequently. This is indeed stable. However, you will likely be unhappy with the old software and want to install newer stuff. Many of the ways this is done will cause actual instability (bugs and crashes). Also, old software may be missing features or hardware support. If you are a gamer for example, this could be a big deal—especially if you use NVIDIA.

Things are a bit better than they used to be with tech like Distrobox and Flatpak.

The frequently updated distros can actually be “more stable” for the same reasons as above. However, every once in a while some package is going to have a bug that may hit you before it is found. Arch or EOS are examples of such distros. They have massive software repositories that probably contain everything you will ever need. If you use one of these, check out the AUR (user contributed software repo).

Distros that fall in the middle, like Mint or Fedora, are what I would recommend for a new user. Compared to Windows, you will find them very tinker friendly and tweakable. Fedora is more Wayland ready (see below).

HDR is very, very new and is part of a change in core graphics tech from something called X11 to something called Wayland. From this point forward, Wayland is the better bet but, today, the quality of your experience is going to be very dependent of the “age of your software” issue above. For NVIDIA on Wayland, you want very up-to-date versions.

KDE Plasma is the most mature Wayland environment today, in my assessment. Others are coming along quickly. That does not yet help you now though.

Photoshop is going to be a problem for you. The most often recommended replacement for PS is GIMP. Unfortunately, GIMP has been on the verge of a major update for years. GIMP 3 has not shipped yet and most distros ship a far older version (2.10). Version 3 is a massive upgrade. However, you may still find it an unsatisfactory PS replacement. Some people use Photopea online.

Gaming on Linux works really well now. However, multi-player anti-cheat systems are Windows kernel only and so these games are going to be a problem. So, your experience will depend on what you play.

The other stuff on your list will work well. Linux of course has a lot more to offer, especially if you are a dev.

Good luck!

Distros matter. Maybe less than you think.

For the most part, they all run the same software, including the desktop environment (user experience).

So, in many ways, choosing your distro is mostly choosing how it comes out of the box and how much work it will be to configure it how you want after the fact. Some distros will be closer to what you want out of the box. But you can basically turn any distro into any other distro with a little effort.

That said, some choices do run a bit deeper and are a lot harder to change. Package manager, init system, C library, and others are pretty baked in.

Time for Republicans to admit that Trump was a DEI hire.

Sounds like you two agree

You don’t need to wait 4. You will know by the midterms if it will get better or worse.

Democratic People’s Republic of America.

We just need to stop sending oil and electricity. The looting and riots should take care of the rest.

Then we can launch a “peacekeeping” mission to the US. Those are our specialty.

Forget the ambassador. Stop shipping them stuff.

If we are going to be honest, let’s not be misleading.

Nobody is looking to replace C in the kernel just to switch out the language. This is not a “rewrite it in Rust” initiative.

What the R4L folks want is to be able to write “new” code in Rust and for that code to call into the C parts of the kernel in an idiomatic way (idiomatic for Rust). So they need to create Rust interfaces (which they, the R4L side, are doing). This whole controversy is over such an example.

At this point, we are talking about platform specific drivers.

Now, new kernel code is written all the time. Sometimes newer designs replace older code that did something similar. So yes, in the future, that new code may be written in Rust and replace older code that was written in C. This will be a better design replacing an inferior one, not a language rewrite for its own sake.

Core kernel code is not getting written in Rust for a while though I do not think. For one thing, Rust does not have broad enough architecture support (platforms). Perhaps if a Rust compiler as part of GCC reaches maturity, we could start to see Rust in the core.

That is not what is being talked about right now though. So, it is not a reasonable objection to current activity.

I doubt Greg is pulling in Rust until it has been through the mainline. That said, Linus can merge anything he wants.