This is good advice. Django, for example, isn't the hottest tech on the block by far, but that's not necessarily a bad thing. Where some see bloat, others see maturity. There are a lot of QoL features like the ORM, forms etc. etc. that make django a very stress-free option. Also, HN sometimes has a derisive attitude towards turbo-like variants, but still, `htmx` is an objectively good pairing with django as well. It's not quite the same as a framework that has web sockets built in, like say Phoenix+LiveView but I'm not completely sold on that anyway. IMO lingering web sockets have an associated cost that hasn't been fairly considered yet.

All that said, my personal favorite CRUD backend is absolutely servant, but will admit that haskell can be a deterrent to some.

Note since I mentioned Phoenix: It might be suitable to you OP, it doesn't necessarily need things like external static hosting, caches, task queues etc and with LiveView can accomplish plenty without surrendering the front-end to a javascript framework. Look up the emerging PETAL stack, it might be of interest. P(Phoenix) E(Elixir) T(TailwindCSS) A(AlpineJS) L(LiveView).