Learning C# .NET Core for a PWA + server + DB project that a client wanted when he could have done all the backend stuff himself.
I ended up burning out because of that project and the crippling hate for C#.

What is it that you hate about c# ? (leaving aside any prejudice against Microsoft)

Mostly its verbosity and the major shift in mental models and ways to approach problems.

@Berkmann18 these feelings, I believe are mutual within the .net community as well. Meaning the .net community definitely hates the mental model and verbosity other languages have to offer.
In my humble opinion then, your preferences can only drive subjective hate. Objectively, there's nothing wrong with a particular language.

@Berkmann18 and don't get me wrong. I'm off c# programming long way back. Not trying to support c#.net in any ways.
I moved away purely due to the job market and the not so open source nature of .net then, which they addressed with core.

@A4Abhiraj I mean, it's undoubtedly subjective, and at least .NET Core made it possible to develop in C#/ASP on GNU/Linux and seems to have been better than the pre-.NET Core C# and more straightforward than VB .NET ~10 years ago (i.e. when I learnt it and then dropped it).

And I'm sure if PHP were the language that my then client's client had in their stack, then it would possibly be just as frustrating (especially as a predominantly full-stack JS/TS dev).

And nowadays, I use C#/ASP .NET Core 3 at work, so the "relationship" has softened, but the project's constraints and what I mentioned above left a terrible taste. And I'll pick Node.js or even learn and use Go/Rust if I had the choice.

@Berkmann18 I believe the strangest thing for a ts guy to move to c# is interfaces.

@A4Abhiraj Having learnt Java years before, it felt really similar; and I've never been a Java fan.

@Berkmann18 yeah me neither. Achieving the simplest things in java sometimes requires shitloads of boilerplate.

@Berkmann18

sorrym, what verbosity ?

3 lines of code (YES 3) are required to make afully functional API REST server.

How is it "a lot" ?

*Disclammer : .Net 6.0 preview

@NoToJavaScript For the most basic API and server in .NET Core 2-3 with enough features to support a PWA/SPA, you'll need A LOT more than that (even excluding configuration) from what I've seen and used.

I guess in .NET Core 6, a lot of the boilerplate code is gone, but I highly doubt you could have a fully functional API that satisfies the requirements I had to deal with on the two .NET Core projects I worked on (or currently working) on.
Feel free to point me to a production-ready PoC of that; I'll Love to see how much code I can delete on the API code.

In-before: why not upgrading to .NET Core 6 (or 5)? It's an enterprise-level project that the Solution Architect wanted to keep consistent with the other projects, and some of the packages used to have limitations for younger versions.