I’m building a project-for-fun right now in Node.js. Between Node and Socket.IO, I have found an extremely amazing level of productivity, especially considering this is my first foray into both.
The project is starting to get a little big, with lots of interconnected parts, and I occasionally break old features while adding new ones. I could be doing more TDD, but static type checking is important too, as there will potentially be a lot of types in this project. TypeScript is really neat, and I think I’d like to do more with it, but as I ruminated in the shower on were this project might be heading, I wondered if introducing TypeScript into my project was anathema to the core ethos of Node.js.
So, with the idea in mind that my project might one day run in a multi-process, perhaps even cluster-like environment, hopefully encouraging other people to contribute both code and content, I wonder if introducing TypeScript (or rather, finishing the port I started today) is a very good idea. None of this is to say that there is anything wrong with either Node or TypeScript. I’m just wondering if they make good bed-fellows.
I’m curious to hear your thoughts. You can reply here on Tumblr, through my site theme on Facebook, or on Hacker News.