Thank you, Carlos, very much, for writing this book. That was a lot of work!
Why would you, Python developer, be interested in Grok? Why not learn about one of the myriad other Python web frameworks instead? Kevin Teague in a recent reddit thread put it very well, so I'll just quote him:
Forget all those Django, TurboGears, Web2Py, Pylons arguments, Grok is where it's at ... Why Grok?
- Schema and model are not tightly coupled: use objects from Zope Object Database, LDAP, SQLAlchemy, Web services, etc. and be able to auto-generate forms regardless of the persistence implementation.
- Convention-over-configuration: Introspects your code, so that you get the benefits of succinct, less-typing benefits convention, without forcing you to layout your software orthogonal to it's purpose. e.g. doesn't force "models" into a models module, "views" into a views module, if you have a Book model and Book view, you can put them in the same book.py file.
- Well packaged (mostly, Grok 1.1 provides a lot of fixes to the dependency tree), so easier to manage deployments. Also core parts are individually packaged, so re-useable outside of Grok (primarily of interest to Plone developers).
- Cavemen are way tougher than Ponies!
What does Grok the caveman himself have to say about a book on Grok? Or about any book, even, as he can't tell the difference?
ME GROK FIND BOOK!
ME GROK LIKE HAS MANY PAGE
MANY MANY PAGE SQUIGGLE!
ME GROK THINK SQUIGGLE ARE FLY DROPPING?
BOOK GREAT MAGIC!
ME GROK TEAR OFF PAGE
PAGE NICE AND CHEWY TO EAT
PAGE GOOD MAKE FIRE WITH
PAGE GOOD WIPE BOT[censored]
Um, sorry about that. I think we should let more literate people review the book instead.
ME GROK JUST KIDDING!
ME GROK LOVE BOOK
ME GROK LEARN ALL ABOUT WEB APP
ME GROK WONDER WEB APP BETTER EAT THAN MAMMOTH?