Totally agree with these iterations of libraries. The latest craziness is their authentication story for ASP.NET. Their new libraries try to fix old design flaw

Totally agree with these iterations of libraries. The latest craziness is their authentication story for ASP.NET. Their new libraries try to fix old design flaws but at the same time leave out functionality from the original membership, role, etc. providers. So for now, their libraries work if you're building a play website but need a lot of know how and customization for a real web application. It's frankly reckless. For someone new starting on the stack, there is at least three different API's for this and they are all supported. It becomes a cat and mouse game of following employee blogs, official blogs and official documentation (which stays at a "hello world" level) to fully understand what the gaps are. I've decided for my own side projects to start using Django and Postgres. I can be pretty much be confident that two years from now whatever version python, Django and Postgres are, my gained experience and knowledge will still be very relevant as the maintainers of these projects don't have a mandate of building a brand new API, or what have you every year.