[Web-SIG] Announcing bobo

[Etienne Robillard]

Hi,

It is suggested that most web frameworks authors aims at a very (wide?)
audience and bet that most peoples are bozos, clowns, or idiots. I think
this rationale might work in some cases, because users of thoses
frameworks indeed might not have all those hard-core technical
knowledges about, say, URL routing, WSGI or even schema migration.

However, is that the preferred way to design web frameworks or should we
assume that the "user" is foremost an intelligent and respectful
"developer" ?

My hypothesis is that web frameworks can sometimes negatively influence
a programmer efficiency to resolve a simple programming problem. I think
this is particulary true when web frameworks are made restrictive: the
available solutions are largely influenced by/for popular or
community-accepted scenarios, thus shadowing or putting in the dark
unconventional solutions.

In a sense, this is perhaps an ethical problem for web framework authors
and not very related to web programming in general..

Lastly, I don't know really if most people have "complex requirements".
In my experience however "basic requirements" are still largely not
understood by popular "full-stack" web frameworks.

Best regards,

Etienne

Jim Fulton wrote:

> To some degree, this is the approach that Zope 3 took,  It (strongly)
> encourages you to separate application implementation from
> configuration.  This was motivated by a well-intentioned desire for the
> kind of flexibility I think you're advocating.  The result was elegant
> but hard to deal with.  I think it's great to have this flexibility when
> you need it, but in my experience, 99% of web applications don't need
> this sort of flexibility and the methods needed to support the
> flexibility become a tax.
> 
> My design for bobo is based on the assumption that most people don't
> need a lot of flexibility while some do, where the former is the common
> case.  It tries to make simple applications very easy to create, without
> making it hard to address more complex requirements.  I feel good about
> bobo's ability to deal with simple applications. Time will tell if it
> accommodates more complex applications. :)
> 
> This discussion falls into the larger debate of configuration vs
> convention and explicit vs implicit.  I tend to prefer explicit, but am
> wary of systems that require a lot of configuration (having built one
> :).  Most systems try to strike some balance, as does bobo.
> 
> Jim
> 
> -- 
> Jim Fulton
> Zope Corporation
> 
> 
> _______________________________________________
> Web-SIG mailing list
> Web-SIG at python.org
> Web SIG: http://www.python.org/sigs/web-sig
> Unsubscribe:
> http://mail.python.org/mailman/options/web-sig/robillard.etienne%40gmail.com
> 
> 


-- 
Etienne Robillard <robillard.etienne at gmail.com>
Green Tea Hackers Club <http://gthc.org/>
Blog: <http://gthc.org/blog/>
PGP Fingerprint: AED6 B33B B41D 5F4F A92A  2B71 874C FB27 F3A9 BDCC