I encountered a quote recently that "Rails is omakase, node is street food."
It struck me as being sort of applicable to the "what is" question around
pyramid.
Most web frameworks *are* omakase ("I, developer, leave all my decisions to
you, all knowing framework author person"), while pyramid is dim sum.
This means lots of choices, but very few that cannot easily be undone or redone
when a situation requires change. These choices are presented in a regular
and therefore understandable format, which actually keeps the number of
concepts you have to understand to be useful w/ pyramid pretty small while not
reducing one's flexibility or power. T The only two things pyramid forces you
to use are the configurator and the router. With such a small core, he
learning can be bite-sized (though I don't think I've seen it presented as such
other than perhaps groundhog).
Pyramid makes writing and using extensions and plugins stupidly easy, so
creating your own personal framework tailored to your own personal usecase or
style of development is a natural outcome over time with pyramid. This
quality contrasts the usual outcome over time for framework usage which usually
results in bloat, framework vivisection, anger, depression and general
arthritis followed by new framework selection, porting, rewriting, rinse and
repeat.
-w
d. "whit" morriss
Platform Codemonkey
[email protected]
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
