About Me
My name is Paul Bissex, and e-scribe.com is my consulting business. I build web applications using as much open source software as possible. From September to June I teach web design and other important non-photographic professional skills to photographers. In the '90s I wrote technology commentary and reviews for magazines, newspapers, and web publications, including Wired, Salon.com, FamilyPC, the late lamented Web Review, and the Chicago Tribune. Feel free to email me.
Colophon
This runs on Django, served by Apache and mod_python. The database is SQLite. The operating system is FreeBSD, on a VPS hosted at Johncompanies.com. Comment-spam protection by Akismet. Vintage topo imagery from the Maptech archive. The markup engine is Markdown.
The Book
I'm co-author of "Python Web Development with Django", an excellent guide to my favorite web framework. Published by Addison-Wesley in October 2008, it is available from Amazon and your favorite technical bookstore as well. Click on the book title above to learn more.
Pile o'Tags
Stuff I Use
Akismet, del.icio.us, Django, dpaste.com, Emacs, FreeBSD, Freenode, jQuery, LaunchBar, MacPorts, Markdown, Mercurial, OS X, Postfix, Python, SQLite, Subversion, TextMate, Trac, Ubuntu Linux, wmii
Spam Report
At least 45600 pieces of comment spam killed since January 12th, mostly via Akismet.
Django, Rails, and PHP
Sam Newman has posted a useful high-level comparison of Django and Rails on his site. In it, I think he hits on one little-discussed reason why these two projects are grabbing so much mindshare right now:
[Rails and Django] ... historically would have ended up being written in Perl or PHP - but ended up being written in Ruby and Python respectively.
When I heard DHH speak at OSCON, he mentioned switching to Ruby after giving up on trying to make PHP do the kind of stuff he wanted to do. Back in July I asked Simon Willison (of the Django team) about PHP; he said that both he and Adrian Holovaty had worked in PHP for years, but it was Python that "gave us the flexibility we needed to pull everything off."
In other words, Rails and Django are web frameworks for people who are sick of PHP. That's a big market.
On the other hand, it's likely that if those people stick around, the Python and/or Ruby communities and the emphasis they put on craft will have a positive influence on the newcomers. Worked for me. Python was the first language I got serious with after several years of PHP work, and the influence of the community was at least as significant for me as my prior experience in C, Pascal, Prolog, Forth, and whatnot.
Haha, very big market. I'm looking for stop using PHP after several years of playing and developing with it.
I love Python, but Dreamhost is putting me on trubble with Django... so I am considering Rails (again). Maybe someday I'll have the time to switch my PyQT apps to Rails.
Post a comment
Comments use Markdown syntax. Your comment will not appear until approved, which may take a few hours or more. Spammers will be torpedoed.
Search
Feeds
RSS feedAtom feedRecent Posts
Programming and Ice Cream
4 comments
Back in Action
11 comments
The iPhone keyboard doesn't suck
2 comments
Recent Comments
akahn
Programming and Ice Cream
9 days ago
Joe Brandt
Programming and Ice Cream
9 days ago
sharon fisher
Programming and Ice Cream
9 days ago
Max
Let's play a game: BASIC vs. Ruby vs. Python vs. PHP
11 days ago
mzee.richo
World's ugliest Django app
22 days ago
Banibrata Dutta
Python one-liner of the day
24 days ago
Gour
Back in Action
42 days ago
Older Posts
Credits
Copyright 2008
by Paul Bissex
and E-Scribe New Media
Interestingly a large amount of people 'switching' to ruby and python because of rails and django are stillusing the new languages like hacky PHP apps. Movement to a new language/famework doesn't neccessarily result in an improvement in software quality - in fact the reverse can often be the case!