For me, that actually worked better. If you start with a fully loaded framework such as Django (even though it is an awesome framework too), I found it difficult to fully understand whats going on in the background. For example, I personally don't like all batteries and prefer to only have the core web functions out of the box. Flask works for me because it just about gives me enough and not much or too less. I don't want to necessarily build my own WSGI layer but I do want control over how I create/save my user details.
Also you don;'t really need to learn Jinja etc. separately. Flask does enough to get you started. For example, I can easily build routing using app.route() decorator in flask which in the back is using Werkjeug. I honestly don't know much about werkjeug itself (yet) but that did not stop me from building a fully functional web app. Of course, if you really want to get in the details, you learn the individual libraries that gives you flexibility to build a real work production app. YMMV
I respect this but I definitely think it's not for everyone. My personal style works better when I'm scratching an itch--so I want to build an app, I learn how to build it in Django, and then as I become more familiar or push limits, I starting trying to learn what's going on behind the scenes. That, or I'm forced to, to implement some functionality that's not "batteries."
Mostly I think it's nice to know "this goes here, this goes there" and have nice obvious examples of where to go next.
Just looking at the front page and tutorial for flask, I wouldn't be thrilled about it. Writing SQL, for instance.
Did you find any good videos about Flask while learning? I see in your profile that you are/were also in the learning process. Would you like to connect on Skype or via email?
Comments
For me, that actually worked better. If you start with a fully loaded framework such as Django (even though it is an awesome framework too), I found it difficult to fully understand whats going on in the background. For example, I personally don't like all batteries and prefer to only have the core web functions out of the box. Flask works for me because it just about gives me enough and not much or too less. I don't want to necessarily build my own WSGI layer but I do want control over how I create/save my user details.
Also you don;'t really need to learn Jinja etc. separately. Flask does enough to get you started. For example, I can easily build routing using app.route() decorator in flask which in the back is using Werkjeug. I honestly don't know much about werkjeug itself (yet) but that did not stop me from building a fully functional web app. Of course, if you really want to get in the details, you learn the individual libraries that gives you flexibility to build a real work production app. YMMV
I respect this but I definitely think it's not for everyone. My personal style works better when I'm scratching an itch--so I want to build an app, I learn how to build it in Django, and then as I become more familiar or push limits, I starting trying to learn what's going on behind the scenes. That, or I'm forced to, to implement some functionality that's not "batteries."
Mostly I think it's nice to know "this goes here, this goes there" and have nice obvious examples of where to go next.
Just looking at the front page and tutorial for flask, I wouldn't be thrilled about it. Writing SQL, for instance.
Did you find any good videos about Flask while learning? I see in your profile that you are/were also in the learning process. Would you like to connect on Skype or via email?
sure I can give you some pointers. My contact info is in my profile (just updated)