RobCrusoe

I find it amazing that there are so many incorrect criticisms of dotnet being made in this thread. It’s honestly as though a number of people with barely any experience with the platform have decided they’re experts and come in to tell everyone else how terrible it is. I shudder to think how many other threads about technologies I know less about also suffer from this affliction.

> If you don't want to write any unit tests, for which there are a myriad of reasons not to, whether you're prototyping, throwing together a small once and done for a client, etc. Then it's just a massive waste of time and gets in the way.

A massive waste of time? Adding a constructor and one line to startup.cs is a massive waste of time? Just how long does it take you?

> It's also something that if you're not working regularly with it can be very mysterious and when it fails, fails at run-time, quite inscrutably sometimes.

If DI fails it’s usually just because you’ve forgotten to add that one line to the startup.cs, and the error you get will tell you that. Can you give me a concrete example of how DI is inscrutable?

I think that claims about a thing should be based on observations concerning that thing, and not based on a folk memory acquired through other people’s attitudes and biases.

A lot of people’s opinions about dotnet are not informed by anything, they see Microsoft in the name and decide to drop snide remarks about how bad it must be, as you can see already from this thread.