(disclamer: I work in Flask, never wrote anything in Django, but have some idea about how it works - also work with Rails, which I guess is a similar beast)
I would guess it's because of simplicity of making basic app. If you main goal is to provide web interface for data manipulation (dashboards, APIs), there's little need to understand how it works and write everything yourself (as you will probably do when starting in Flask until you find all the right plugins and/or write abstractions you need).
Max is a life enhancer for tech & entrepreneurship. Which seeks to blend both to build innovative products or services for the world that solves hard problems.
Yup it's actually a replica of Ruby for Django. Which is why data scientists will work with Flask more than Django.
Due to its huge learning curve that follows to just to understand it and use it fully because you are really going past the microservice and API aspects of it.
From humble beginnings at an MSP, I've adventured through life as a sysadmin, into an engineer, and finally landed as a developer focused on fixing problems with automation.
Are you saying flask has a huge learning curve while also advocating Django? Or am I misunderstanding? I've done professional work in both; flask was significantly easier to get people productive in fastest but I did lay solid foundations following good patterns and recommended extensions like flask-talisman and co.
Max is a life enhancer for tech & entrepreneurship. Which seeks to blend both to build innovative products or services for the world that solves hard problems.
(disclamer: I work in Flask, never wrote anything in Django, but have some idea about how it works - also work with Rails, which I guess is a similar beast)
I would guess it's because of simplicity of making basic app. If you main goal is to provide web interface for data manipulation (dashboards, APIs), there's little need to understand how it works and write everything yourself (as you will probably do when starting in Flask until you find all the right plugins and/or write abstractions you need).
Yup it's actually a replica of Ruby for Django. Which is why data scientists will work with Flask more than Django.
Due to its huge learning curve that follows to just to understand it and use it fully because you are really going past the microservice and API aspects of it.
Are you saying flask has a huge learning curve while also advocating Django? Or am I misunderstanding? I've done professional work in both; flask was significantly easier to get people productive in fastest but I did lay solid foundations following good patterns and recommended extensions like flask-talisman and co.
Ahh.. its my bad I wrote wrongly. I was referring to Django for steep learning curve.
To me it is more like of a overkill to use Django. Which Data Scientists just prefer to get it done with a quick & dirty solution.
Depending on who you talk to they might not even know of the concept of clean code or TDD.
When they are building a data product as it is not part of their job to do it.