Same here. I used Django since version 1.3. Did jab a bit with flash but always find myself back at django after a while.

Same, working since 1.4. DRF is not that bad, but it's much harder to learn than FastAPI. Looks uglier too and the configuration just isn't worth it, especially for smaller projects. I'm still working with DRF at my job, but personal projects are all FastAPI now. Will probably change most of the job project to FastAPI anyways.

@@komkaitkanchai8766 wow i'm amaze to see django vets here, i just learnt making basic django apps.

with Django Ninja introduced, I don't think API should be a problem anymore in Django

Why use ORM even 😂😂 just use normal SQL

same too, I transitioned from php to python 3 years ago. python is so much cool.

@@wolfmeowmeow developp in something you like, so you'll dive deeper without even noticing and you'll become way better and your time way more valuable.

Hey how does flask feel compared to laravel? I've been using and loving Laravel for years now but i want to try something else cuz php still feels kinda ancient, how would you compare the two? Is Laravel more similiar to Django instead? (I would only need it for backend, usually my frontend is angular/react)

@@TortelliniSRL you should stick with it, laravel is good, you just need a backend framework doesn’t mean you have to learn all of those are exists.

@@wolfmeowmeow i agree with you for that but learning multiple framework kinda is my job ahahaha, anyways in our company we main laravel for backend and our cto is now giving us the chance to switch to one that could potentially suit our needs better, the learning curve won't be a problem since it will most likely be a gradual change (most of our stuff still run laravel backend), i was just wondering if it was worth to switch (if the writing time efficiency / potential less package support ratio was)

I mean, not giving a definitive answer is good and all, but an opinion at the very least would be appreciated

@@Voidstroyer The pros for each library showed their strengths and where they should be used. Django enforces a specific file structure and layout and comes with the python-esque "batteries included". I would hazard a guess its used in larger projects because of that structure so there is less conflict between the teams (e.g. frontend guys are primarily in the templates, backend would be between models and views). Flask is extremely light-weight and you can build something functional in an extremely small codebase (I believe he said 47 lines of code excluding the HTML template). One of Flask's major pros is you can choose what library you want for every part of the process, don't like the templating engine? Cool, pick a different one. Want to write your SQL by hand and bypass the ORM entirely, np. In that way it completely gets out of you way and allows you to choose the right tools for your use case. FastAPI seems to follow Flask's general structure but adds batteries for an extremely common use case which is RESTful APIs (while not throwing in the kitchen sink like Django) and makes use of the type-hinting in python 3 avoiding issues the other two had to contend with prior to that feature being added to python. Its relative youth would be a double-edged sword, for greenfield uses you don't have any technical debt in the form of backwards compatibility with existing code, however on the other hand how well has it been battle tested? On pypi its still listed as Beta, should I expect breaking changes in the future? If you are confident you can keep up with its development it probably would be the most performant of the three especially with all the performance enhancements coming in python 3.11 and later.

@@davidmcken Thank you very much for the detailed explanations of the pros/cons for each choice.

I can programme big and fast Web projects by Flask only ?

@@youssefchaabi5402 why not?

@@Deadlious Flask good in scaling ??

@@Deadlious OK bro thank you

@@youssefchaabi5402 what did you go with? Flask?

@manny I'm definitely not an expert, but I would say FastAPI given that you'll probably want to build backend microservices for your app, and then just create frontend clients (for web, android, ios, etc) that communicate with your FastAPI backend.

I did the same, fastapi also gives you more freedom since django only lets you use its dependancies while fastapi lets you install and work with whatever, not to mention faster and more lightweight only the tools you need

me too

fastapi has awful docs

@@meizufluxx but faster and better development if you learn it right?

@@NishantCosmos no fastapi is awful because the docs are awful. they desperately need an api reference

For any "basic" app the documentation is enough, the only times I have had to dive into the fastapi code was for more customized OAuth and even then the source code isn't that cryptic, I've been using it for over a year and it's my go to for rest APIs that don't require massive scalability. The biggest difference with flask and django is that if forces you to make a distinction between frontend and backend, ideally only making a rest api that a static frontend consumes, but I see this as a better way to build web apps as it forces you to learn about frontend frameworks that are way better than anything a python framework can provide.

Ca va, mon ami.

I can tell you more. In large projects nobody writes code without typing :D So you made a good choice :D

Django-ninja is a good choice

@@huacai168 it really doesn't matter what you use, end of the day its all about python and how you're implementing your python mechanism into web.

@@wolfmeowmeow tech debt is a real issue lmao

true

true, if i would start again i would learn flask then learn django, as flask helps you understands how django does things under the hood.

Yup flask is a gem

Flask is complicated because of code written in one file,,, there is no MVT structure which is easy to wrte codes in different files

Django is super easy that the most complecated fastapi and flask

Once you work long enough using Django you end up knowing what is going on inside. What you find in django is a very well developped structure. I personally dont care if fastapi is faster, because I can just scale horizontally my django service. microservice. In the long run the bottleneck is 99% of the time the database. Whe programming you want a mvp asap you don't get to waste time trying to integrate stuff, you just want something that works well fast, that's why I'll stick with Django. That being said I it is not very good when it comes to handling websockets, I'll usually go with node

Celery is an standalone tool. You can use it with Flask, FastAPI and any other framework.

Brother can you suggest best project in flask , for Intern resume.

@@josedominguez8782 True, but I was thinking about celerys direct integration to django - "django-celery".

@@dipenketanbhaidave154 Issue tracking system

thank you!

How do u merge the two together?

@@jonathanidioseph5101 not the original commenter but we do the same where I work. Front end services just either make HTTP calls to the backend and/or can listen to or send RabbitMQ (sometimes pub/sub) messages. They're all microservices so each component is it's own discreet unit that just pass data between themselves

@@jonathanidioseph5101 you merge front and backend through rest api, where the frontend makes requests to the backend

​@@asii_kresourses to learn microservices with django-react ?

Agree fully, the batteries Django includes are hard-won battle scars from those that went before you. There is usually very little benefit in re-inventing the wheel, focus on whats unique to your app. For smaller projects you should be designing to avoid those issues in the first place.

@Francisco Mendoza Torres yes

@Francisco Mendoza Torres yes it is a killer feature

Why do you need DI in Python? As far as my understanding, DI is just bundling different modules/components together at RUNTIME. In static languages like Java and C# you'd need DI. In Python, you can assign any variable to any object at runtime. I would like to know why you'd need it in Python? Python has DI built-in isn't it?

@@subipan4593 makes it easy to setup tests and test, thus, you can achieve extremely high coverage

@@ND-gn8tc ONLY when you're using static languages like Java. Python is dynamic language that can change data types in RUNTIME. No need for DI in python.

It's called FAST API.

You could say you've been "hitting the bottle" for the last few months! *badumtsss* (I'll see myself out now...)

I can programme big and fast Web projects by Flask only ?

"vuejs front end instead of Django"? Really? How are Django and VueJS comparable?

@@BehruzbekOtayev i think he meant that he is not using the front end template engine provided by django out of the box. Using django just to build the api. Which is actually norm in production for quite sometime already.

I would love a fastapi + vuejs tutorial!

@@yasayah7289 take it separately, "vuejs tuto rest API" and "fastAPI tuto". The only glue is to serve your static files generated by vuejs.

Vuejs and flask is match from heaven as well

@ragsdale9 can you provide the few lines of code for the fllask example. Im getting the same error

hey I was able to find the solution on github haha!

Do you mean functional in a paradigmatic or in an efficiency way?

@@robin888official in a paradigmatic way

@@facundogoiriz7323 Can you give any examples? I moved from a functional language to Python and the whole language is by no means functional. Still, Pythonic way of writing most things fullfills my need for "clearness" and conciseness. I am using Flask too and I think it's very neat.

async support is incredible too

1 month later, it's really great. Wow.

_"Still think that all the frameworks are being updated constantly so I'm not too dramatic about the "best choice""_ - Right on point sir. I agree that Django Channels is a bit complex, but there have been prod applications that have integrated Django Channels decently. Check out baserow.

@@vhaangol4785 Thanks for pointing! I'm gonna take a look at that one!

Can we create database files by coding?