It's not node.js that feels unstable -- it's the shifting libraries that make it feel unstable for me. I was going to do my project in node.js, and might still, but a project that I get maybe a few hours a week is just not going to work with something moving so fast.
I think if I was on a startup with it, I'd feel comfortable as long as my first patch or two was accepted on the projects on which I depended.
I've been working with nodejs a lot lately. Nodejs itself is fine, it moves a fair bit between releases itself but it's predictable. It's built on V8 which really is fast and has not failed me once.
The worst part are the libraries. Some are outdated, even 'major' things. That scares me a bit. Even worst is when you bring a pull request updating the library to work with a later nodejs and get no response.
I've had major issues with sockets, which really sucks because to me that's a major appeal of nodejs. Non-blocking code and sockets make realtime really approachable. But nowjs didn't work for me, randomly working between browsers. So I rewrote it using socket.io, same technology at a lower level. Same issues. Then I finally got response from the dude from nowjs saying it's a problem with socket.io 'wait for 0.7' crossing fingers, knocking on wood.
That's not serious, that gives me the @#$##$^.
I don't think people should go out there, make website promoting their awesome libraries and the thing just falls over after 3 api calls.
I've been playing around with node.js and express a bit lately and can't find any resources or examples of a project using sqlite. Does anyone know of any?
Anyone else feel this way or should I just get over it and get back into it?