My goal with this blog

I write about relevant changes in the way that people use the web and how startups are built to provide services and products for this ever changing wonderful thing we still know as "the web." As a former entrepreneur turned early-stage investor, my greatest hope is for this to be useful to other folks that are like me in the hopes that they can avoid some of the mistakes I've made.

The Crack that is Productivity

So there have been two raging debates recently that have made me think about productivity and tools.

The first was ignited by one of the Y-Combinator companies, Reddit, reimplementing their site in Python after having done the first version in Lisp. Since they are a "Paul Graham company" and since Paul Graham has spent a long time convincing us thatLisp was the ultimate language (even while speaking at Python conferences), the geek blogosphere and comp.langs.* newgroups were full of debate about what this meant with respect to whether Lisp was all that Lispers make it seem.

The second (but related) debate came from a post on O'Reilly Radar where Tim O'Reilly pointed out that Ruby books have raced past Python books in terms of sales. This observation lit up a debate about the relative merits of the two languages, their web frameworks, and their communities.

These discussions are mildly interesting to follow, but at this point only just mildly. Both Ruby and Python are incredibly productive tools, especially when compared to their C++/Java/C# alternatives. Having slogged through half of a Lisp book, I would imagine that Lisp would also fall into the Ruby/Python camp but for its poor libraries.

So why do I follow the threads at all? Because it was one such thread back in 1995 that led me to Perl, and another one in 1999 that led me to Python. In each of these cases, the deltas in productivity were so great that it was a worthwhile investment to follow what the alpha-geeks were discussing.

It's just that now we're a year into the web frameworks brouhaha and yet it seems like the discussion has stagnated. Yes, Rails is much better than J2EE for productivity with small teams. But Rails and Django are eerily similar in the way they attack their problem (as are the half dozen other web frameworks that have sprung up in the Python world to try to be "the next Rails"). Why is it that almost no one is talking about novel languages/frameworks/approaches that are truly new to the way in which people solve web problems? Where are the approaches that are as different as dynamically-typed, interactive interpreter-enabled languages like Python was to Java six years ago?

I spent some time this last week digging around for what that next novel thing might be. This led me to a fairly mediocre book (which would have been great as a series of blog posts) called Beyond Java which had a chapter at the end about a Smalltalk framework called Seaside which takes a continuations-based approach to handling the processing of web requests. Really interesting stuff.

I'm not sure about whether Seaside is the type of measurable leap forward that I'd like to discover, but I do know that I would like to see some of them energy that is going into arguing about whether Ruby has really eclipsed Python or whether the Reddit rewrite proves that Lisp is just another one of those insanely productive languages (as opposed to The Most Insanely) shifting to discussing the pluses and minuses of languages with continuations support in them.

At the very least, tracking such a debate like this would surely help me in finding my next fix.