James and Ben ask 'what makes Pylons different from other web
frameworks?'

This is totally backwards imho.

The strength of Pylons is not that Pylons is different from all the
other (Python) web frameworks but that it takes a more rigorous,
standardized, modular, comprehensive approach. That and the friendly,
knowledgeable community.

Seriously, this is a great Friday topic (o.k. I'm a little late to the
party).

Pylons is the only framework that isn't taking shortcuts, and that is
trying to bring the Python web framework community together by erasing
differences.
(o.k. I may be talking out of my, uhm, nose, but that is what it looks
like to me, a perpetual newbie)

I came to Pylons, clip-clop, clip-clop, in my quest for 'The Holy Grail
of web frameworks', passing by ASP, PHP, Zope, RoR, Django, and TG.
It started with a search for a templating system to use in our large
Oracle db, ERP type web application(s). Determined to taste the 'Open
Source' waters I had heard so much about, I tried Python and fell for
'Dive into Python', with help from 'Learning Python'. I don't like to
use the word 'elegant' with Python because Python is so unpretentious
but it fits. 

Now armed, and with the search narrowed to Python (but with many a
glance over the shoulder at RoR, and ASP), I entered the forests of
'Python: the only language with more web frameworks than keywords'.
Arriving at the walls of Zope, the fortress proved unpenetrable. Django
charmed with a Google Tech talk
(http://video.google.com/videoplay?docid=-70449010942275062) where Jacob
Kaplan-Moss talked about the wrong way to do templating and I thought:
'hmm, exactly the way we do it.' However, the more I looked the less I
was sure that the differences were that great. TG also beckoned with its
promises. The skys were dark. Hope was lost. Then, the waft of an elixir
called sqlalchemy that solved the riddle of composite keys, parted the
clouds, and led back  to the path of WSGI, which was maintained by
Pylons. and worked. In this small community were worthy and esteemed
knights.

O.k. lets stop the metaphor there as its getting tortured.

As far as branding goes, I think the Pylons brand is strong and the
electricity grid is a good metaphor and has many possibilities. 
Perhaps a green lightning bolt for a favicon?

I admire all the open source projects but I think maybe TG and the
Django brands have suffered a bit in quality from their rush to market?
I applaud Kevin Dangoor for elucidating that Zope, TG, and Pylons are,
more and more, converging.
http://groups.google.ca/group/pylons-discuss/browse_thread/thread/40899c
b2db03bcf6/15de0eed76c10bfb?lnk=gst&q=dangoor&rnum=2&hl=en#15de0eed76c10
bfb

I hope the natural evolution of all these frameworks will eventually
result in the best of breed. I think the Pylons people doing the heavy
lifting are helping to bring this about by making sure everything can
interoperate (through standards, wsgi), because that, it seems to me, is
the only way forward.

Now to finish off. I think a tag line is important. It is only a small
part of a brand but what is easily memorable.
Below are the hackneyed tag lines that wandered through my mind until I
hit upon one I liked, the last one.

So in the spirit of fun, I put this out as a tag line competition, can
you top: 'Pylons - carries the load'?

Pylons 
- 'No shortcuts - end to end integration'
- 'No shortcuts - approachable end to end integration'
- 'Pylons does the hard work for you'
- 'Pylons handles the wires'
- 'Lighting the LAMP'
- 'Pylons - Python web development that carries the load'

- 'Pylons - carries the load'

I like this one, with the electrical and works connotations. I think a
tag line should be short - memorable rather than explanatory. A succint
summary of Pylons can follow.



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to