3 ms·
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 real
by keyle 16y ago
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.
- weixiyen 16y agoWould you care to elaborate on the errors you are getting? I've been using socket.io with no problems.
- keyle 16y agoHappy to send you some source code, maybe you can shine some light? msg me your email @keyle on twitter?
- randall 16y agoI know of some guys working on a project called NowJS that should take care of some of your socket woes. http://nowjs.com/ http://nowjs.com/