4 ms·
I've tried FastAPI recently, as the idea matured, I came to regret the decison. It's not bad, in fact it was very pleasant to get started with, yet I found myse
by WhatsName 4y ago
I've tried FastAPI recently, as the idea matured, I came to regret the decison. It's not bad, in fact it was very pleasant to get started with, yet I found myself missing and reinventing the wheel as compared to django. I develop with Django since 2015 (1.6 or so), to me it is the goto for any web related project.
I used to think my distaste for new and upcoming Javascript frameworks is a sign of getting old and not being as adaptable as I used to. But nowadays my thinking has shifted to seeing it as a instant loss of productivity with little upside.
Just like musicians don't switch instruments every time they see something shiny. Neither should we, or at least without feeling guilty about it. Mastery takes time.
- yuppiepuppie 4y agoI couldnt agree more with this statement. FastAPI was good for the prototype. Then when you want to go and do something a bit more complicated, it becomes a hinderance more than a help.
- barapa 4y agoCan you provide any specific examples?
- ensignavenger 4y agoI've used a variety of Python frameworks, Django, Flask, FastAPI, and I'm always coming back to DJango and wishing I had just used it from the beginning. Django Ninja brings some of the nice features of FastAPI to Django- https://django-ninja.rest-framework.com/ https://django-ninja.rest-framework.com/