3 ms·
Hm... Django isn't hard. Mostly the problem is caused by using a framework. Since you throw a tool at things which only needs like 5% of the whole Framework. Ev
by merb 12y ago
Hm... Django isn't hard.
Mostly the problem is caused by using a framework. Since you throw a tool at things which only needs like 5% of the whole Framework. Even if it is as modular as Django/Rails etc. it's just unnecessary.
Thats why more and more Developers love tiny Frameworks/Tools like golang/Sinatra/Flask
- smoe 12y agoI totally agree with the 5%, that's why I never used Django before for a real project and preferred Flask mostly. But for this project it made sense since I'm using almost all of its documented features and some undocumented ones like model swapping plus a couple of extensions. My point was, that it doesn't have to be hard to slow you down. Whatever framework you choose, you will get stuck at some point. A Django developer will have starting problems with Flask, glueing together the basics and choosing a folder/file layout (or changing it later), while for me, I had a very quick start with django building a prototype in no time but then got stuck a lot later on while customizing an having other opinions that the opinionated framework.