signpost
"Flask Web Development"
"Flask Web Development Web-based application development Python's real,"
"Flask Web Development" is suitable for beginners Python Web development?
text
"Flask Web application developers to develop Web-based real Python's", O'Reilly "book series Animals" and "dog book" should be a lot Flask primer recommended for beginners to use, but this book is really for beginners yet ?
Python Web framework is very large, such as Django, Flask, Tornado, Web.py, Tornado no contact could not be evaluated, Django and usually "heavy duty" linked directly rarely recommended for beginners, Flask and the Web. py belong to the light frame, the internet was the Flask compared with web.py, there is a very interesting Blog are interested can take a look a word about Flask and web.py comparison (very old blog), which is better what little there please choose.
It is worth mentioning that the introductory tutorial documentation micro-channel public platform, is based on written web.py
Here we Tucao about micro-channel public platform maintenance documentation team, you can not do so out of error of level ......
"Flask Web" Web development is the development of my introductory book, when he bought the first edition, the second edition of the book later, also bought a second edition. This Blog is not the focus of the discussion Flask framework, but to discuss the book itself, if you choose to study Flask, the following comments to you makes sense.
CONCLUSIONS :: direct throw this book is not for beginners , or that "now" is not appropriate.
This conclusion is based on several reasons
- Template rendered content
- Domestic chapters can not practice
- Content too "System"
In fact, some of these reasons are a little picky, but the starting point of these ideas are two: "For Beginners" and "want to quickly build a simple web services developers."
Template rendering "obsolete" ......... it?
I do not know the answer to this question, but at least in my mind, the template is rendered "obsolete old stuff", because the current popular before and after the end of the separation, are React, Vue, Angular three front-end framework, rather than need background control template rendering.
Flask and Jinja2 almost always simultaneously filed, the whole idea of this book are based on the realization of the project Jinja2 template engine, which in the release of this book is not any problem, but now the development of front-end technology have made it this book can not keep up, and now advocates a "before and after the end of the separation", the front and rear ends by Rest API interaction.
Personally, I gave up direct template rendering, directly from the Vue start of front-end technology.
Domestic chapters can not practice
"Flask Web development," a great feature is the whole point of the book is a project to complete the tutorials throughout the book, is to complete a blog system, like book reviews said the same, compared to only explain the fragmented code of other books this is undoubtedly good. But, "Chapter VI E-mail" will be a hurdle, because the contents of the book is based on the well-known cause of Gmail's ...., we can not use Gmail's SMTP service, Gmail can not even log in, the inevitable need to beginners online search for alternative solutions (I was looking for an alternative SMTP service 126).
Why is it inevitable? Skip this chapter will not do it? Because the contents of this book inter-related, not this issue is resolved, follow-up content can not advance, for starters, the answer is clearly no, it is learned there is a point to do.
As the cloud platform later in Chapter 17 domestic rarely used even more not to mention
Content too "System"
This may be one reason the strangest, the "system" also point do wrong? Of course yes, but still that reason, not suitable for beginners. In my opinion a beginner can write a view function, operation ORM, learn to use a hook, cross-domain configuration, has been able to complete a simple web app. The database migration, factory function, blueprint, unit testing, not a beginner can hold the contents of living? But this knowledge is cross in the book, and are based on engineering structures (factory function, blueprint, etc.) were forced to start the second part of the entire contents from here when I was a novice of directly discouraging.
Even beginners jump this reason, for now, I do not really like to use engineered structure Flask, why? This may need to be clear, "Why should I use Flask?", Because light and fast. Flask I choose not to develop a commercial project (if the purpose is certainly to use SpringBoot a) build a simple service, but in order to quickly complete a POC short period of time, or when learning clustering technology, these needs are often only a few dozen lines of code can be done, why bother using the directory structure engineered it?
Recently wrote their own blog system prototype, cross-domain configuration, the view function, ORM, web token based login manager, also was less than 140 lines
in conclusion
So what this book is the right way to open it?
Personally, I think the content of the previous Chapter 5 of this book (the first 60 pages, the whole book is about 200) are a beginner you can see, there are many important concepts, but then further recommended that only Chapter 14 , more contradictory point is Chapter 14 is based on an engineered structure written directly to see there will be some difficulty ...... so now the book in my hands is equivalent to a book, when you need to read chapters need, and most of the time need to deal with it again in order to use the sample code, but from beginning to end, this book I have no system from start to finish.
Above, I hope this book entry Flask want people little use.
####
For more Haytham original articles, please pay attention to the public number "Xuju Long":