Right. I don't know if this changed significantly with 6, but my experience from previous versions have been that as soon as you start adding things like caches, authentication middleware that interacts with certain other components, or rewrite requests or responses in other ways it soon becomes a goose chase across the web and incomplete documentation.

This is what comes to mind to me from GP's mention of crazy abstraction mazes.

A lot of this stuff was fiddly a long time back, before dotnet core, but it's all pretty sweet these days.

For example, `AddMemoryCache() ` gives you a memory cache with the default settings - or you can change them by using the options argument. Request rewriting is really simple too, and even authentication is relatively straightforward.

I get what you mean about "crazy abstraction mazes", but thankfully over the past few years we've been trending away from the madness of ludicrous inheritance hierarchies that were sold as "clean code" and dogmatically hoovered up by junior devs (including me, once upon a time!).

It does get a little complicated when you try adding in the middleware components, and it doesn't Just Work. Frequently then you end up at some GitHub readme file as the only documentation (for first-party Microsoft components) with some very brief examples, maybe with some samples that don't quite show how you'd want to do what you want to do. Then you start digging in the source code and learning how the guts of aspnet core work.

I would agree that bailing on dogmatic 2000s OOP has been an improvement.

I think The command and observer aspects of WPF are really elegant and OOP patterns certainly have their place.

But app development isn’t a pretty place where time crunched developers are expected to carefully design complex data structures…..at all.

How much boilerplate and configuration does "dotnet new web" generate?

That was the entire source code. There is a project file, but it's incredibly simple and they are meant to be human consumed/edited nowadays.