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.

There is an old anecdote about this kind of situation; Postman (P), Recipient ®:

R: what are you doing? P: I left a notice that I tried delivering a package and you weren’t home. R: But I clearly was! P: <shrugs> R: <bashes postman’s face in> P: WTF, MAN!? R: It wasn’t me, I wasn’t home.

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.

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