Yes, use Rider and .net core - everything works on non-windows platforms (working on .net from osx right now, deploying to linux)

Avoid vscode for C# development, unlike TS/JS (which is top of the line), the support for C# even in core is toy level.

What do you think is lacking in C# extension for VS Code vs TypeScript? I would expect a better experience with C# (in terms of tooling) because the language is typed.

It just doesn't work nearly as well - even on simple .NET core solutions created from CLI intellisense chokes up, refactoring doesn't work, it's nowhere near the quality level of TS.

Even TS support is pretty lackluster compared to Rider's and VS' C# support.

Yes, JetBrains rider is IMO superior to VisualStudio these days, and I run a huge amount of C# code in production on Linux. It was definitely crippled in the past but it's a first class citizen in the .NET ecosystem now.

Rider is incredibly fast and superior to VS in all aspects but one - its debugger is terribly broken. VS will break on my line of code that crashes. Rider will crash somewhere completely unrelated. My code is very much async, that might be what kills it. I ended up doing everything in Rider, but debugging in VS.

Rider also doesn't allow you to move the current instruction to somewhere else on getting an exception IME.

I'm actually use both. Debugging story in Rider is a bit flawed compared to VS. But due to very large codebase Rider is a bit better in performance.

Also relevant... can you learn it, build it and deploy it for free?

I've always thought the whole ecosystem looked really productive, and the code I've had to review occasionally looked well structured and readable. But when I was starting out MSDN cost a fortune and I've never really considered trying to learn it.

Especially with lsp-mode, C# on Linux (or Mac) is a great experience using emacs.

https://0x85.org/csharp-emacs.html

I use Sublime and it works well.