The Montoya Herald, a weblog about Blueprint, jQuery, design, music and life, publishing on the web since September 2005. Written by Christian Montoya: developer, designer and entrepreneur.

The Montoya Herald — ChristianMontoya.com

Search

Buy My DVD!

Like What I Do?

My Amazon.com Wish List

On this domain

Elsewhere

Making the move to Python

Posted on March 3, 2008.

For the past few years I've been almost exclusively dedicated to PHP development. At my last job I was forced to learn Perl so I can legitimately say that I know it, but considering that PHP came about because Perl was too hard to use, I've always preferred PHP. With good reason too; it's fast, it offers decent OOP with version 5, it integrates tightly with Apache and MySQL, and it's very familiar to me as a person who did a lot of development in C. Recently, however, I've hit some roadblocks in my attempts to optimize PHP, and I had to find an alternative that would solve those problems. I've settled on Python.

In all honesty, another language is just another language, so I don't care that Python is more syntactically elegant than PHP. My reasons for using Python, and why I would actually make such a significant move, are:

All of these are things that are both, a) not in PHP, and b) essential to the kind of high-performance work that I want to do. So it's decided: I'm going to start doing my new projects in Python. I'll still be using PHP a lot for applications that I have to manage, or for working with Wordpress, but I'm excited about working with Python; it seems like the Python community is full of people who really care about performance, and there are a lot of smart things being done there (just look at Django, SQLAlchemy and Mako).

Get a trackback link

1 Comments

  1. Lucas Murray on March 4, 2008

    Welcome to the new world. Being a PHP-to-Python mover as well I can say that you will find quite a lot of things in Python that are much nicer and easier to work with than PHP due to the complete and thourough OO approach of the language. =)

Leave a comment

Use Markdown or basic HTML. For posting code, use Postable. Please keep comments respectful and on topic.