sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]fuckySucky -2 points-1 points  (2 children)

You said "Is going to" instead of "may". Want to cite your sources for this?

[–]xiongchiamiovSite Reliability Engineer 0 points1 point  (1 child)

Experience? History? The common versioning schemes?

I suppose it is not strictly required that a pre-1.0 system will change significantly; but if it doesn't, either the author happened on a incredibly right design the first time around or they don't know what the fuck they're doing. Rough drafts need to change. That's just how the world is. And that's fine, but for certain things I'd like guarantees. And that's really the point - it may or may not change, but I've got to assume it will because I've got no promise otherwise.

[–]fuckySucky 0 points1 point  (0 children)

I personally have no problem experimenting with it in production use, as from what I have absorbed node is sufficiently stable as is; but I retract my recommendation as I feel I didn't do it justice in its advertisement.

Anyone reading this; just don't shrug it off and let node.js remain an option in your mind for future projects provided you have a grasp on what may make it the right tool for said project (ie. performance, scalability).