Simplifying Grok/ZTK

Grok is wonderful software, but it needs to go on a paleolithic diet.   A role model is the  Pyratemps templating engine.  Just 500 lines of code! Here is their philosophy:

 

It seems that perfection is achieved not when there is nothing more to add, but when there is nothing more to take away.
— Antoine de Saint-Exupéry: Terre des hommes

Technology always develops from the primitive, via the complicated, to the simple.
— Antoine de Saint-Exupéry

These pages explore what needs tob e done to simplify Grok.  

It is good to keep in mind Occam's razor:
“Entities (concepts) must not be multiplied beyond necessity”
It is not lines of code which we need to minimize. It is the concepts. Historically people speak of productivity as lines of code. "That is like measuring progress on an airplane by how much it weights" Bill Gates. Functinn Point Analysis is better. Measuring number of unit tests is also a good measure. But both of those encourage complexity. Minimizing the number of concepts (classes) maximises productivity.

Simplifying Security

Grok/ZTK security is both too complex, and too slow.  At the bottom is the general zope.security model.  On top of that is the

zope.securitypolicy model.  On top of that is the Zopache security model.  Way way too much.  

 

Worse yet, the three are quite different.  The user model is to click check boxes to assign permissions to roles, and roles to users.  

Everything else are unneeded concepts.  

 

 

 




I invite you to Register and then link to your own blog postings and software packages..

Powered by Zopache, Grok, Zope and ZODB

Robots Crawl This