On Mon, Dec 6, 2010 at 12:49 PM, Chris McDonough <chr...@plope.com> wrote: >> This move is natural based on BFG's history, and the new situation of >> future Pylons newbies, which is forcing Pyramid to be more accessible >> and simpler out of the box, rather than just being a "hackers' >> framework" as BFG was. > > (An aside, unrelated to this discussion: this statement puzzles me. > It's not like BFG has really changed that much since becoming Pyramid. > It's not "just a hackers framework" now that its name was changed? > Really?)
BFG had a steep learning curve due ZCML and Traversal. The difference may be more in emphasis and documentation than in software. By emphasizing imperative configuration, moving the ZCML examples to the back of the manual rather than as the primary way to configure Pyramid, talking up URL Dispatch, and adding view handlers, makes Pyramid a lot more accessible to developers who don't come from a Zope background, and to new developers who might otherwise choose TurboGears/Pylons/Django/Werkzeug. -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
