nfgu

Funny thing: in the last couple years I've seen way more back buttons broken because of backend idiossincrasias than anything else.

It is super common to see "Don't use your back button" messages after placing orders on e-commerce websites.

On the other hand, most frontend developers writing SPAs just use react-router or something like that (instead of reinventing the wheel) and it just works.

I've seen countless unmaintainable applications written using popular MVC frameworks that required simple modifications, but the next person in line wasn't able to understand what the hell was going on.

Popular frameworks are not silver bullets, but apparently it's popular on HN to think so.

It is entirely possible to import things like EntityFramework, Razor and Identity Framework without using ASP.NET MVC itself.

Just because the framework uses them by default it doesn't mean they can't be used separately.

You can use Razor Pages or a router like Nancy[1] without having to roll your own ORM or View Library.

[1] https://github.com/NancyFx/Nancy

Someone isn't necessarily "rolling their own stack from scratch" just because they eschew a framework.

You can always import libraries into your project for the critical stuff, instead of using the whole framework.

Even Laravel itself imports third-party libraries such as Symfony, which you can use in your project without importing Laravel.

You can use rendering libraries, ORMs and session management libraries without a framework.

I think it's way nicer. I much prefer environments like Sinatra, Express or Flask than full-blown MVC frameworks.