Ask HN: What would be your stack if you are building an MVP today?
Definitely old schools. I am building a MVP  right now(kinda building my parachute while jumping off the plane)and I went with Django. And here is why.
1. Very vibrant community of devs and time-tested open-source libraries.If you want a multi-tenancy there is a library for that. IF you want stripe integration there is one for that. If you want &quot;fully built out&quot; services, then we have a plethora of free and paid templates. There are folks here(HN User rlawson)who have built many side projects using Django that they have monitized. if that monetization is your goal, then time is money and Django is your friend.
2. Very easy to deploy. This is a Major major requirement for someone like me(dabbling in webdev). Even after the demise of Heroku hobby dynos, there are things like Railway.app which lets you git deploy app, try it out and then scale it if you want.
3. Lastly, Javascript not necessary- I am a &quot;hobby python dev&quot;. I don&#x27;t have the inclination nor the time to learn yet another Javascript framework. I have an idea, know a bit of Python and I want to iterate it on my idea fast and get to the customer ASAP. Meaning, I can deploy a MVP without having to dabble with JS while jumping through all the different web pack configurations. A big win for me.
So, &quot;boring stack&quot; definitely.