Yup. Build it, ship it, and spend the majority of the dev time writing integrations that aren't really made any easier by any particular framework.

I tried Django but I liked Laravel better. Because I knew it better. Exactly.

Fair enough. But Laravel is apparently cut from similar cloth so you'd be in agreement with the general philosophy here?

For sure as far as MVC frameworks go. Those are two of the best. I enjoyed Django when I worked on it. It was enjoyable to work in and had a lot of power. It was clearly a great framework. Also tons of big sites use it. And if a boss somewhere said they wanted the team to use it at some point in the future I would be totally happy about that decision.You cannot go wrong using django in the least as far as I'm concerned.

Yeah good luck getting something to market quickly if you aren’t in any way familiar with any of those technologies

I think you misunderstood the intent. Constantly optimizing your toolset instead of building a startup with what you already know is a very common form of bike shedding and is one of the hardest things for some developer-founders to get past.

The goal of a startup is to build things quickly, so actually being able to build things quickly is important. If you know a set of tools well you can work quicker than using a perhaps better set of tools that you do not know well. That is an important point to make to people like me who like playing with new toys

I build things quite fast with flask and bootstrap, perhaps now with fastapi. If I have spare time I'd rather spend the time validating ideas or tech in new domains rather than learning more new tech that's just similar to this.

I did not dismiss the article, I've read it. I just replied to the pretty strong statement that his choice is a "go-to" stack for building SaaS.

I don't see it that way. After multiple comments in one direction it was healthy to have someone say, "Wait a minute. Let's not forgot why we're here and what we're here to do."