4 ms·
This is fine if you build a website or a small app. But I wouldn’t recommend this approach for a more serious/big app. You will end up with unmaintainable soup.
by ggregoire 8y ago
This is fine if you build a website or a small app. But I wouldn’t recommend this approach for a more serious/big app. You will end up with unmaintainable soup.
- scarface74 8y agoLike another poster said. This would be useful if you’re using a server side rendering framework like ASP.NET MVC and you just needed a little bit of AJAX. You would maintain most of your HTML, routing logic, etc. server side.
- bobjordan 8y agoMy experience building a large flask app with jinja2 templating (large in that the app is ultimately a mix of ERP/manufacturing management/customer+supplier portal). The intercooler approach combined with flask blueprints and template folders is extremely maintainable. It is easy to comprehend all aspects of what is going on at any time. Can get a decent developer up to speed to be productive with it, within days. The vast majority of businesses would never need a heavier framework than this.