Skip to main content

Python: Almost Famous

Long ago, I worked at a company named Echobridge. The lead engineer was a guy named Noel Rappin. He was a Squeak fan. I set about trying to convert him to Python. Years later, I picked up a copy of Jython Essentials. He was the co-author.

Recently, I started talking with a guy name Ben Bangert. He had the idea of tying together Paste and Myghty into a new framework similar to TurboGears, but more devoted to pluggable micro applications. I donated some code, but mostly said, "No thanks, I'm far too busy with Aquarium." His framework, Pylons, has taken off like a shot and is far more popular than Aquarium.

When I went to PyCon, I sat next to these two guys at a WSGI get together. One of them had an English accent. I remember he said, "We had a look at the other Python Web application frameworks, but didn't find them suitable for our needs, so we wrote our own." I just thought to myself, "Yeah, welcome to the club buddy!" Months later, a project named Django became immensely popular overnight. It wasn't until I saw a video with the authors of the project that I recognized who they were.

I was so close to being hip, slick, and cool ;)

I'm sure we all feel like that sometimes.

Comments

Anonymous said…
Seeing as the other Django guys are Americans, I guess that must have been me :) -- Simon Willison
Anonymous said…
Noel's at it again.
http://manning.com/books/rappin
Anonymous said…
Hey jj -- look at the interesting things you find when you Google yourself...

Anyway, thanks for the mention... and you did talk me into Python, just on a bit of a delay...

-- Noel
jjinux said…
Once again, I was almost famous. Guido van Rossum kept asking me to come work with him on something "really cool" at Google. I said "not right now" because a) I was in the middle of a startup b) I was too burnt out to survive the Google interview process c) they hadn't yet opened up the San Francisco office.

Google just announced what he was working on:

Google Apps Engine
Unknown said…
> Google just announced what he was working on:
> Google Apps Engine

Well, it's been five years. I joined Google 3 months ago (working as a developer advocate at YouTube), and just a few minutes ago, I submitted my first change to Google App Engine! I happen to be sitting in Google's San Francisco office (although I normally work in Mountain View).

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p