I’ve just launched the newest addition to SketchPort, a word guessing game, which runs on Node.js. Players get 90 seconds to draw the word that is given, while the other players try to guess it.
The game uses the same SWF as the draw page, so all users get a clean image with no pixelation, and the standard tools, such as alpha, blur, and layers. Also, the viewport is synchronized, so the user who is drawing can zoom and pan freely.
This is my first time deploying Node.js code into a production environment. I’m happy with the
post-receive hook in git, which made running the new code after a push pretty easy. I’m also happy with npm, which I think is one of the best parts of Node.js.
On the other hand, I haven’t figured out how to neatly break Node.js websocket applications into separate processes. Maybe I’m just spoiled from using Flash Media Server, but it seems like pretty basic functionality to break applications and instances of applications into their own processes. I’m looking into using Seaport, the new nginx websocket proxying, or most likely a custom Node.js solution using cluster or named pipes.
Overall, working with Node.js is fun, because it runs well, has good documentation, and adding new features is as easy as