Metju

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

While they do work, the UX is kinda gimped (knowing Micro$oft - that's on purpose).

Source: using Rider Snap in Ubuntu in daily work

Recent Linux convert here. Had some small background with it due to use at work (through WSL, unfortunately 😅). When Windows became too overbearing and intrusive for my own taste, decided to take a plunge and created a dual-boot setup with Bazzite (of course on my private machine). It was honestly refreshing to see stuff run with the same (or sometimes even better) performance.

This short anecdote now leads me to the conclusion; is it as good as we think it is?

Imo: hell fuckin' yeah. It gets the job done and respects me as an end-user (with the trade-off of "some manual work might be required").

Also, as a side-note: I live in the EU; I grew tired with an overbearing, salesman/rapist-like mentality of MS (and Windows, by extension) while reaping benefits of some modicum of privacy regulations. I cannot even begin to fathom how fucked the situation is where ppl don't have these protections to rely on.

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.

Some of recommendations I did not already see, that are not-that-well-known; all of these are various flavors of melodic death metal:

Parasite Inc. - Once and for All

Avatar - Bloody Angel

The Agonist - Panophobia (unfortunately, the band is now defunct)

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