I'm very pleased to announce SocketStream 0.3.0 is out and has been pushed to npm.
This is the end result of months of experimentation and development, lessons learned from previous versions, and many kind contributions from our growing community of users (now over 2000 watchers on Github!).
As many of you have been successfully running pre-release versions of 0.3 over the last few months, I'm happy to declare 0.3.0 stable, with the obvious caveat that SocketStream is still *very new* software and any external production deployments must be done with caution. Don't use it for anything super-important (or financial) just yet.
As you may know, my original plan was to invest time promoting SocketStream 0.3 with screencasts, building example apps, and expanding www.socketstream.org.
I still fully intend to do all these things; however, I've learned over the years to always work on what you feel most passionate about at the time - so called 'mood driven development' as @antirez puts it (http://antirez.com/print.php?postid=252).
Over the last month or so (and particularly after NodeConf) I've felt the urge to take a second pass at some of the features in SocketStream 0.3 to see how we can design and architect them better - especially the Request Responder API (which I'm the first to admit is not as simple or elegant as it should be).
As a result of all this experimentation, development of the next major release (SocketStream 0.4) is now well underway. It's not going to be a revolutionary change like 0.3 was, but an evolutionary improvement that builds upon the solid foundation of ideas in 0.3.