I think the author was dead on despite some confused points - the number of problems that node is the best solution for is a fraction of what its currently being used for. It seems obvious that it's popularity is tied to server side javascript.
Node.js is good for solving problems I don’t have
41–50 of 61 posts
Re: Node.js is good for solving problems I don’t have
#42Exactly, node is useful for solving problems that you don't have. So you wouldn't use node for them, then. The answer to your own question is your own statement. Node makes it possible to do completely new things that would be difficult to do otherwise. I take exception to this statement: "Node enthusiasts are front-end coders not wanting to do server coding." The number of engineers who only do server-side programmi…
"Node has been a blessing for me, as a frontend engineer, because I can finally code servers in the same mindset as I write client-side javascript. " That was precisely the author's point. You'd rather stick with what you know then bother to deal with traditional server side techniques.
I'm a backend engineer. Have been for years.
Node.js works for me.
I don't think much else needs to be said.
Re: Node.js is good for solving problems I don’t have
#43Earlier quoted context omitted.
"Node has been a blessing for me, as a frontend engineer, because I can finally code servers in the same mindset as I write client-side javascript. " That was precisely the author's point. You'd rather stick with what you know then bother to deal with traditional server side techniques.
Uhmm, I've been writing server side code for the last decade. I've also been writing front facing code for just as long. JavaScript works well for Node because it is a language that has evolved to be asynchronous. Not because some front-end web monkey n00bz know JavaScript. Although that is certainly a plus. Node.JS shines when you need to write network applications. It was advertised for this purpose by its creator.…
Traditional server-side solutions SUCK at this. Try writing a non-blocking server-side WebSocket server in PHP and distribute the load across all of the cores.
Wouldn't the traditional way to do it server-side be to just write it in C/C++ or Java with a thread pool? Or if you prefer the evented model, Python+Twisted isn't old enough to really be traditional, but is pretty widespread; and some Java server-side apps have been moving to an async model as well.
Re: Node.js is good for solving problems I don’t have
#44Exactly, node is useful for solving problems that you don't have. So you wouldn't use node for them, then. The answer to your own question is your own statement. Node makes it possible to do completely new things that would be difficult to do otherwise. I take exception to this statement: "Node enthusiasts are front-end coders not wanting to do server coding." The number of engineers who only do server-side programmi…
Parallel requests and async callbacks have been hallmarks of server programming for decades. You'd have to be pretty young to think this is novel. Good protocol library designers have always exposed some mechanism for kernel-assisted polling (such as the file descriptor for the TCP socket of an LDAP connection). So, Node solves problems we've already solved, only now using the second most poorly designed common produ…
With that attitude we should have stopped at FORTRAN. What next, drive a Model T instead of a Civic?
Nobody knowledgeable has said that async coding is novel. What matters is that node.js is a simple(r) and effective means of writing asynchronous applications.
Re: Node.js is good for solving problems I don’t have
#45The whole website is a PR/FUD base for Mark Logic. Check their Wikipedia page too. http://en.wikipedia.org/wiki/MarkLogic I guess they're tyring "to fully utilize the potential of the internet".
Actually they mention Mark Logic in the article a couple of times, but what they say totally stands (at least as an argument) on its own. I could care less about Mark Logic. I do care about what the article says, and I agree with it.
Having skimmed the article I found it relatively unenlightened. What do you agree with?
Re: Node.js is good for solving problems I don’t have
#46Earlier quoted context omitted.
Parallel requests and async callbacks have been hallmarks of server programming for decades. You'd have to be pretty young to think this is novel. Good protocol library designers have always exposed some mechanism for kernel-assisted polling (such as the file descriptor for the TCP socket of an LDAP connection). So, Node solves problems we've already solved, only now using the second most poorly designed common produ…
Right, that's why most servers nowadays are written in this mystery platform that you failed to mention.
C.
Re: Node.js is good for solving problems I don’t have
#47Your friend might not be nodejs, but it might be .... Javascript. One way to speed up data processing on the server is to avoid processing it as much as possible and delegate such processing to the client side. Hence, Javascript is your friend there.
Re: Node.js is good for solving problems I don’t have
#48Earlier quoted context omitted.
"Node has been a blessing for me, as a frontend engineer, because I can finally code servers in the same mindset as I write client-side javascript. " That was precisely the author's point. You'd rather stick with what you know then bother to deal with traditional server side techniques.
Uhmm, I've been writing server side code for the last decade. I've also been writing front facing code for just as long. JavaScript works well for Node because it is a language that has evolved to be asynchronous. Not because some front-end web monkey n00bz know JavaScript. Although that is certainly a plus. Node.JS shines when you need to write network applications. It was advertised for this purpose by its creator.…
I don't actually think anyone should be using PHP. Just like MySQL gives relational databases a bad name, PHP does the same for server side programming. And yes actually trying to write a server in PHP would be ten times more insane. Node.js might be nice for writing servers but so is Twisted or straight Python, Erlang, C, even java with threads as someone mentioned.
Re: Node.js is good for solving problems I don’t have
#49"I don't like brussel sprouts."
Then don't eat them.
Re: Node.js is good for solving problems I don’t have
#50Earlier quoted context omitted.
I use node for new cutting edge things which Django and Python can handle, but not as easily as node. Like what?
Like massive concurrency? Websockets?
For rather small values of "massive" perhaps (i.e. single-server?).
Once you reach into realms where the label "massive" comes into play the importance of per-host performance is usually dwarfed by attributes like robustness and maturity.