Re:We switched to Node.js: the good and the not so good
by mukundmr on Monday January 14, 2013 @07:48AM
(#5054406)
from a long term maintainability perspective, javascript can be notorious. you could always follow a disciplined approach for development to help with maintainability, but that applies to all programming languages. i don't see anything about javascript that makes it more maintainable especially for large projects.
[ Parent
| on HN ]
Re:We switched to Node.js: the good and the not so good
by julien on Monday January 14, 2013 @08:01AM
(#5054443)
It's not the language, it's the people, the community.
Re:We switched to Node.js: the good and the not so good
by necrodome on Monday January 14, 2013 @08:16AM
(#5054480)
what's different about node community from ruby community? are you sure that's not confirmation bias?
Re:We switched to Node.js: the good and the not so good
by julien on Monday January 14, 2013 @08:58AM
(#5054637)
Well, again, most of the dependencies we used in Ruby did not see any update in the 3 years we've been using them. We also reported several bugs in those libraries/dependencies which were never fixed. This led us overtime to use our own branch of all the significant dependencies we had (including the MySQL gem for EM, the redis gem... and several other key ones).
Most of node modules are still in active development. As I've stated in the blog post, that's a pro and con, but we estimated that the pro was greater than the con :)
Re:We switched to Node.js: the good and the not so good
by LargeWu on Monday January 14, 2013 @09:21AM
(#5054705)
What leads you to believe all of these node modules that you now have dependencies on will still be in active development in 3 years?