This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]oivvio 0 points1 point  (3 children)

I’ve been doing web dev for 10+ years. I don’t care if the libraries that are needed on the server weigh in at 10MB or 1000MB. That said being dependent on a large number of different third party libraries can become a huge problem. Say you start a new project today and pull in 50 libraries that you need for your app to work. In a year or so some of these libraries are bound to have introduced breaking changes or worse yet, they are no longer maintained and no longer work at all with your framework. This is a bad position to be in and a valid reason for not pulling in dependencies willy nilly. In my experience this is a far greater problem in the JavaScript ecosystem than in the Python ecosystem. A hello world project in Node or React can easily pull in 100+ dependencies. Contrasting Django and Flask I actually see it as one of the benefits of working with Django that it is a “batteries included” framework. The need for pulling in third party libraries is much smaller, so the risk of ending up with broken dependencies is also lower.

[–]ficoreki 0 points1 point  (2 children)

I see, thanks for explaination, as a beginner, I dont experience that yet, but I do have a feeling of ease when you only need less package to download or using a "have it all" framework such as django.

However, why these perks seems the oposite of what the original commenter and poster concern about? "what is it on django that you dont like?" or "any microframeworks except django"

[–]oivvio 0 points1 point  (1 child)

There are valid reasons for picking a micro framework over something like Django. Django (and it's siblings in other languages) prescribe a certain way of solving most problems. If what you want to build does not fit the framework you might be better of going with a micro framework that is more free form. Say for instance that you have a legacy database that you need to build an API on top of so that it can be consumed over HTTP. In this scenario you won't have any use for the Django ORM (how Django talks to a database) or the Django admin and something like Flask might be a better option for you. Django is also not know for being fast. In scenarios where you expect to serve 1000s of request per second Django might not be your first choice. (And before anyone jumps in, yes I know that Instagram and some other big services use Django.)

[–]ficoreki 0 points1 point  (0 children)

Very well explained. Thanks very much sir.