3 ms·

It depends on what you are building. Server side can cover so much ground these days. It could be the Ghost blogging app which was recently released or we could

by gexla 13y ago

It depends on what you are building. Server side can cover so much ground these days. It could be the Ghost blogging app which was recently released or we could be talking about the muscle behind Google. Node covers a lot of "good enough" space for what a lot of people are doing. The people who complain the loudest about Node are likely those who are working on things which aren't covered by that "good enough" circle. I wish people would use real life project examples or include the sorts of work they do when they makes these kinds of arguments. It would help us see where this person is coming from.

solomatov 13y ago
>It depends on what you are building. Server side can cover so much ground these days. It could be the Ghost blogging app which was recently released or we could be talking about the muscle behind Google. Consider for example a rich text editor, or diagram editor with a complicated automatic layout. Doing such things in JS is extremely painful.
dsl 13y ago
The majority of people writing Node code don't know what that "good enough" space covers. Or they get so excited hitting something with that hammer that they stop looking in the toolbox. Node is fantastic for rapid prototype development, or tiny little startups that need to do the absolute minimum amount of work so they can finish before running out of money. Everything goes sideways when these cute little Node apps get pushed out to real production use (if you measure things in anything other than dollars per second, you don't get to chime in here and redefine production). Then the heavy hitters have to come in and patch Node itself, or rewrite it in another language. I've gone in to a growing startup over a weekend and saved them $1000/mo in AWS instances by rewriting a Node app in 30 lines of Go. I hate to cite examples of real world projects in threads like this, because it just devolves into "OMG YOU NOOB THAT WAS FIXED IN THE BASHFUL BADGER RELEASE" when said fix was the result of a bug you opened or a patch you submitted.

by gexla 13y ago

solomatov 13y ago

>It depends on what you are building. Server side can cover so much ground these days. It could be the Ghost blogging app which was recently released or we could be talking about the muscle behind Google. Consider for example a rich text editor, or diagram editor with a complicated automatic layout. Doing such things in JS is extremely painful.

dsl 13y ago

The majority of people writing Node code don't know what that "good enough" space covers. Or they get so excited hitting something with that hammer that they stop looking in the toolbox. Node is fantastic for rapid prototype development, or tiny little startups that need to do the absolute minimum amount of work so they can finish before running out of money. Everything goes sideways when these cute little Node apps get pushed out to real production use (if you measure things in anything other than dollars per second, you don't get to chime in here and redefine production). Then the heavy hitters have to come in and patch Node itself, or rewrite it in another language. I've gone in to a growing startup over a weekend and saved them $1000/mo in AWS instances by rewriting a Node app in 30 lines of Go. I hate to cite examples of real world projects in threads like this, because it just devolves into "OMG YOU NOOB THAT WAS FIXED IN THE BASHFUL BADGER RELEASE" when said fix was the result of a bug you opened or a patch you submitted.