While I agree with the basic premise, when I see the words "Pain points of Node.js" here is how I react:
A) Node.js provides a means of writing back-end logic in Javascript. Who in his right mind would want to do that, when appropriate, i.e. non-scripting, higher-performance, languages are available for the task?
B) The term "pain point" seems to be a favorite among seagulls: usually consultants, who swoop in, makes noise, crap on everyone, and leave. We do already have a word for that: they're "problems".
1 comment
1 u/LoftyGoat 08 May 2016 00:36
While I agree with the basic premise, when I see the words "Pain points of Node.js" here is how I react:
A) Node.js provides a means of writing back-end logic in Javascript. Who in his right mind would want to do that, when appropriate, i.e. non-scripting, higher-performance, languages are available for the task?
B) The term "pain point" seems to be a favorite among seagulls: usually consultants, who swoop in, makes noise, crap on everyone, and leave. We do already have a word for that: they're "problems".