seanmonstar

As I said last night, I don’t see how nodejs is the solution, by itself, for a web application that talks to many services. I’d still say that MVC is the best solution we have seen so far. Python has great support for long-running async tasks, talking to various databases, and the like.

That said, I love my JavaScript. Here’s where I see nodejs being a win: writing JavaScript on both sides of the stack feels great, and it gains small amounts of CPU time by making file I/O asynchronous. For other long-lasting tasks, such as resizing an image, you still need to set up a task in a queue for other CPUs to crunch.

I love JavaScript. It’s awesome. But this is an excellent view at why I still think Python has a place on the server. Some of the points I share pain with:

• Very small standard library
• Only a single number type (which is limited)
• No built in module system

I love me some Python, but it’s also very tempting to be able to write JavaScript on both sides of the application. And for now, it’s free!