andhieka
commented
9 years ago I'll uodate you this afternoon
Andhieka Putra Sent from a touch device. Please excuse my brevity. On Dec 16, 2014 11:52 PM, "Eugene" notifications@github.com wrote:
Flask-Blueprint somehow reminds me about our project complexity. Flask are meant for a very small project. (microframework). When we start considering Flask-Blueprint (app based modularity), we are emulating Django framework.
Originally, We start with an idea of guitar practice page. We know that it would be 1 or 2 pages. And Flask will be a good options being an API provider.
But we didn't consider possible feature that we will be integrated in determining the Framework. We didn't consider Social Auth, Database ORM, Code Convention.
As I see some of our codes, there are some codes mimicking what Django Framework has already provide out of the box. Moreover, I find that there are many ways to achieve somethings. There are no conventions in our project which I find it is quite hard to scale later.
I would recommend we start considering Django as an alternative to Flask for our project.
— Reply to this email directly or view it on GitHub https://github.com/guitar-academy/gaserver/issues/8.
Flask-Blueprint somehow reminds me about our project complexity. Flask are meant for a very small project. (microframework). When we start considering Flask-Blueprint (app based modularity), we are emulating Django framework.
Originally, We start with an idea of guitar practice page. We know that it would be 1 or 2 pages. And Flask will be a good options being an API provider.
But we didn't consider possible feature that we will be integrated in determining the Framework. We didn't consider Social Auth, Database ORM, Code Convention.
As I see some of our codes, there are some codes mimicking what Django Framework has already provide out of the box. Moreover, I find that there are many ways to achieve somethings. There are no conventions in our project which I find it is quite hard to scale later.
I would recommend we start considering Django as an alternative to Flask for our project. If we decide to change our framework, I would create a separate empty project branch, then when it is ready, we can compare which is better in term of the DRY (is there any repetitive of the boilerplate code?), code productivity (how fast can features get done?), etc...
After trying Flask, I think Django is easier to learn. (Due to the fact that there are certain conventions to follow)