Skip to main content

Which python web framework do I use - Flask or Django?

Let me take you on a beautiful journey.

Flask:
 
You start to ride a bike.
Being a noob you mess up a lot of times.
And, get hurt over and over.
You learn things now.

Django:

You start to ride a bike.
But, a plot twist.
You learn riding a bike by observing others.
You sit on their back and see how much smoothly they do ride.

Now, either situations are possible:
  • You copy them flawlessly and become a pro.
  • You mess things up badly, end up injuring self and dumbstruck about how things are done.
Now the choice lies with you. You know your caliber better than anyone. 

Coming to the point, Flask and Django are both awesome in their own aspects.

Flask can help you learn and get the feel of how things are carried out in backend development and how frontend can be improved exponentially with a correct backend setup. And the learning curve is much gentle as compared to Django. But the problem lies in doing much on your own messes things up at large scale, hence slows down the production work. 

With Django, you can get yourself settled and ready for professional development, but if you are a beginner, you might end in messing the basics up and staying confused for a long time with the introduction of new concepts. Still, Django is fast and much more efficient in practical terms as compared to Flask anyday. It comes with a useful admin interface, bootstrapping tool, a robust ORM to work with widely used databases like MySQL, Oracle, SQLite and PostgreSQL. Also, the ORM system enables developers to perform common database operations without writing lengthy SQL queries. The built-in migrations tool is pretty useful.


Therefore I would suggest that if you are going to start web development with python, go with flask first, clear the basics first. 
By basics, I mean that you should be good enough to build your own CMS (blogs basically) as they quiet effective in checking your progress.
You should be familiar with words like migration, a bad request, modals, views and all sorts of stuff.

With that done you can surely start your way as a Django developer.
That would be easy to start then.
I also suffered from this confusion once but took the right choice by judging my caliber well!
Labels:

Comments

Post a Comment

Popular posts from this blog

सूनापन

मुद्दत हो गयी उन तन्हायियो को गुजरे , फिर भी इन आँखों में नमी क्यों है  ? तोड़ दिया मोहब्बत पर से यकीन मेरा, फिर भी मेरी दुनिया में तेरी कमी क्यों है ? हसरत है क्यों आज भी तेरी चाहत की मुझे, क्यों याद तेरी जेहेन से मिटती नहीं ? जलजला क्यों उमड़ता है ख्वाबो में मेरे, उस आशिकी की आगज़नी क्यों है  ? सन्नाटो में भी क्यों सुनता हू तुझे मेरी परछाई से क्यों तू जाती नहीं ? इन डबडबाती आँखों को तलाश तेरी, आज भी कहीं क्यों है   ?
6 comments
Read more

How the Python import system works

How the Python import system works From:  https://tenthousandmeters.com/blog/python-behind-the-scenes-11-how-the-python-import-system-works/ If you ask me to name the most misunderstood aspect of Python, I will answer without a second thought: the Python import system. Just remember how many times you used relative imports and got something like  ImportError: attempted relative import with no known parent package ; or tried to figure out how to structure a project so that all the imports work correctly; or hacked  sys.path  when you couldn't find a better solution. Every Python programmer experienced something like this, and popular StackOverflow questions, such us  Importing files from different folder  (1822 votes),  Relative imports in Python 3  (1064 votes) and  Relative imports for the billionth time  (993 votes), are a good indicator of that. The Python import system doesn't just seem complicated – it is complicated. So even though...
1 comment
Read more

What does it mean to “shift testing left”?

What does it mean to “shift testing left”? I used to think shifting left meant starting all these testing activities earlier in the process, but I realise it is more than that: it means  doing different things . Shifting left on testing means thinking about architecture and design differently, considering different stakeholders early and continually. Which in turn means shifting left on security, accessibility, and all the other dimensions of quality that we should care about. So shifting left on testing motivates all kinds of assurance activities, which can stop us over-investing in a solution that was never going to work. It is like TDD on steroids. As an unintended consequence, we can remove much of the traditional work that testers would have to do downstream when they only have late sight of the product. Again, we aren’t doing that work earlier, we are setting ourselves up to never need it at all!
Post a Comment
Read more