3 ms·
I’ve always admired Slack’s pragmatic choice for LAMP, despite the amount of slack it gets (pun intended). Despite its reputation, it still has an amazing commu
by vincentmarle 7y ago
I’ve always admired Slack’s pragmatic choice for LAMP, despite the amount of slack it gets (pun intended). Despite its reputation, it still has an amazing community, ecosystem, and tooling to get shit done.
I’m currently working with Flask/Postgres and it’s simply lacking when you need to scale it (in terms of performance/team size/code size) and there’s not great tooling to take it to the next level. Can’t wait to get back to Laravel on my next project.
- inputcoffee 7y agoI admit, it really makes you think about iterations and MVP in a new way. I am surprised you said you found flask lacking though, because I would have thought they were similar. Can you say more about what you found to be lacking in terms of performance/team, size/code and tooling?
- Deimorz 7y agoFlask is a micro-framework, it's an explicit goal to not have that kind of tooling included: http://flask.pocoo.org/docs/1.0/foreword/#what-does-micro-mean http://flask.pocoo.org/docs/1.0/foreword/#what-does-micro-me... There are lots of Flask extensions and other methods to extend it (relevant docs page: http://flask.pocoo.org/docs/1.0/becomingbig/ http://flask.pocoo.org/docs/1.0/becomingbig/), but it's a framework that practically defines itself around the fact that it doesn't include anything. Pyramid or Django might have been better options.
- ngrilly 7y agoWhat's the problem with Flask and PostgreSQL?...