Daily-driving Nobara with NVIDIA, (almost) no issues whatsoever here.

Granted, I ain’t the person you responded to and it’s anecdotal, but… Yeah 😅

Well, technically, they’re 3rd party problems. But I get your point about seeing this from the end-user perspective.

And yeah, it’s DEFINITELY not fair

Seconding k3d (and, by extension, k3s). If you’re in a market for sth suitable for more upstream-compliant clustering solution (k3s uses SQLite instead of etcd, iirc), RKE2 is also a great choice

I struggled to find things to learn because I installed it and had an out-of-the-box windows experience

And that’s a good thing! Non-technically-inclined ppl are wary of instability issues and having to work with the terminal to fix their daily driver. If the OOTB experience is good and the UX is comparable or better than Windows - they will be more likely to stay.

If someone is accepting the fact that shit might go sideways, is willing to learn through experiencing issues first-hand or simply likes to spend time fiddling with their OS to find the perfect setup for them - that should be the Arch- and Arch-derivatives audience.

Frankly, the problem with socialism (and with anything else, for that matter) is that it takes one high-up enough asshole to ruin things for everyone.

Then again, I have little-to-no proposals to counter your argument, so I guess it’s back to cookies and diabetes for us

It has entry in WineHQ that the license won’t activate, so… Yeah, it’s effed

2 flavors of Fedora with KDE on it:

1. Aurora-DX for some dev work on the side. Once you get used to distroboxing / devcontainers, it’s rock-solid and mean dev environment (saw some minor issues with how certain GUI apps were scaled, but that’s about it).
2. Nobara for gaming (tried Bazzite and it’d prolly work for that purpose as well).

Unfortunately, had to keep Windows on one other machine (fuck you KORG for not providing anything working on Linux), but that’s limited to being a glorified music player now 😄

• .Equals and == have different meaning in C#. Decent IDEs will warn you about that (and yes, that excludes Visual Studio, but that always was crap 😄).
• As for (re)assignments - I don’t see an issue with that, tbh; you only have to be aware of whether you’re using a reference- or value type (and if you aren’t, then let’s be honest - you have bigger problems).

I admit, “canonical C#” looks like shit due to a fuckton of legacy stuff. Fortunately, newer patterns solve that rather neatly and that started way back in C# 6 or 7 (with arrow functions / props and inlined outs).

Tl;dr: check the new features, fiddle with the language yourself. Because hell, with ref structs you can make it behave like quasi-Rust

And what would that equality entail? Reference equality? You have .Equals for that for every single class. Structural equality? You can write an operator for that (but yeah, there’s no structural equality out of the box for classes, that I have to concede).

Hell, in newer C# (~3-4 versions back, I don’t recall off the top of my head) you have records, which actually do support that out of the box, with a lot more concise syntax to boot.

As fir that being Java all over again: it started off as a Java clone, and later on moved in its own direction. It has similar-ish syntax, but that’s the extent of it.

C# on Visual Studio is a fucking nightmare. Switched to Rider on WSL the first chance I had, not looking back.

Then again, if this is running on .NET Framework, there is no choice, afaik. You get a buttplug made of barbed wire in Windows + VS, and you’ll like it

Fellow .NET dev here, switched to Linux for side-gigs recently.

In general, the experience is a lot better than Windows / WSL. Some general remarks on the setup (relevant mostly for Debian-based distros, so YMMV):

• Rider / VSCode suggestion is spot on; go with the former if you have cash to spare and you’re fine with snaps, otherwise - DevKit can do DevKit things (with the only problem here being lack of .dcproj support in VSCode; can be ignored with proper integration test setup).
• Containerization of DBMS: by all means, go for it if you have the resources to spare.
• Possible gotchas:
  • If you’re going to use MS apt feed for .NET runtime / SDK, set up apt preferences to point to their feed for dotnet packages. Otherwise, you’re in for a bad time when running updates.
  • Docker: personally, I recommend Rancher Desktop for this purpose, as Docker Desktop on Windows left a bad taste in my mouth. If you’re fine with the latter, it’s up to your own preferences then.
  • Test containers: if you do use it with anything else than standard, bare-bones Docker setup, you’ll need a custom config; stumbled upon that the first time I tried running integration tests.

At home: FLACs ripped from CDs (prefer to buy albums I enjoy instead of Spotifying them) -> KORG DS-DAC 100 -> TEAC AX-501 -> Elac Carina BS243.4

On the go: The same FLACs on Pixel 6 Pro -> B&O Beoplay HX

Seconding this. B&O know their stuff when it comes to sound (though I’d avoid TWS due to having bad experience with them myself); currently rocking HX, seem to work fine