4 ms·
I was so disappointed with other frameworks since Django was my first. I've come to realize this is widespread as I've learned other languages, but every time I
by Larrikin 7y ago
I was so disappointed with other frameworks since Django was my first. I've come to realize this is widespread as I've learned other languages, but every time I start a new project and setting up the important boilerplate I'm constantly thinking in my head "Django would have just included this or there atleast be a battle tested plugin"
- MattGaiser 7y agoI think it depends on who you are as a dev. A lot want to create from scratch or have it be a handcrafted product, which I can respect. I just like producing cool stuff and don't want to be manually running SQL queries in both dev and prod.
- monsieurbanana 7y agoYour comment comes off as haughty to me, as if you were saying that if you choose not to use a framework like Django its because you want to have a "handcrafted product" and because you don't care about "producing cool stuff", which sounds like a textbook definition of a bad (unproductive) programmer. I assure you it's not, not using frameworks can also be a purely pragmatic choice. If you deviate from their intended use, they can very quickly become an annoyance instead of a time gainer.
- MattGaiser 7y agoI am thinking more about the people who reflexively use Flask as Django is "bloated."
- collyw 7y agoI never really got that unless people were complaining about Django's ORM. The framework is flexible enough that you can use as little or as much of it as you need.