Django Pony – What were they thinking?
Alright, Cal dissed us Django Developers by comparing Django to „Flamework“, the Flicker Framework and finding that Django is definetely unsuitable for large large large scale productions like Twitter, Flicker, Yahoo or the like.
Alright, a point granted is that syncing models to the DB is uncomfortable, deployment is not yet all that great and the template syntax is akward. However, the demand for a mascot, like a Snake and/or Monty Python for Python, Dolphins for MySQL or the Road Sign for Bazaar, has turned the whole friendly Django world glittery pink.
A pony, to be more precise, THE Django Pony
http://djangopony.com/
is the result of this sarcastic comment. Also:
http://code.google.com/p/django-pony/
has sprung up in the aftermath of Django Con.
I implore all of the Django Community: Please, let’s abolish this devilish pony and open a discussion round for a real mascot – as we could use one indeed, but not PINK and not PONY. Or, if we were bound to stick with it, let us at least make it a unicorn, sit a python snake on top of it and call it the Django Unicorn of Death – DUD, and there we go, it would be almost as cool as Tux.
Habemus mascotum – or what else that might be called.
And I was just wonedinrg about that too!
But I like ponies…
Eldest Daughter (in mocking tone): „Daddy are you working on boring Duh-jango AGAIN?! You’re ALWAYS on that computer!“
Me: „Yes, but aha, wait until you see this…“ (types „djangopony.com“ in browser address bar)
Eldest Daughter (now much less mocking): „Ahhh, that’s so cute! Scroll down…“
Younger Daughter (runs over): „What is it? Ah Duh-jango pony, I want one!“
From that day forward I vowed (as would all Fathers with daughters) to defend the pink pony with all my Fatherly strength!