Node.js is good for solving problems I don’t have
xquerywebappdev.wordpress.com
Node.js is good for solving problems I don’t have
1–10 of 61 posts
Re: Node.js is good for solving problems I don’t have
#2I guess I don't understand - is this meant to be an object lesson or warning to people against using the wrong tool for a given application?
The author self-identifies their problem as: "The problem I have is processing a lot of data quickly"
Clearly, then, don't use node. But why write a blog post about not using something? A post involving a lesson learned ("I tried using node for processing a lot of data quickly, and it was terrible!") would have been more valuable.
I fully offer up the idea that I may have missed the point.
Re: Node.js is good for solving problems I don’t have
#3Troll. Post made no sense and came to no conclusion.
"The content server should not need to do hardly any IO. Why would an HTML content server need to write to the filesystem?"
This just shows a blatant lack of knowledge about what constitues IO. FYI, network is IO, writing to console is IO, logging is IO. The point of an evented system like node (and others based around the 'select' or 'epoll' type calls is that you can use one thread to do other things when you are waiting for the kernel to tell you your socket is ready.
Yes, I too get frustrated when 'front-end' people think they are systems engineers or super server coders, but that doesn't mean I am going to write a blog post that goes nowhere about it and completely misses the point of an evented system like this.
Re: Node.js is good for solving problems I don’t have
#4I guess I don't understand - is this meant to be an object lesson or warning to people against using the wrong tool for a given application? The author self-identifies their problem as: "The problem I have is processing a lot of data quickly" Clearly, then, don't use node. But why write a blog post about not using something? A post involving a lesson learned ("I tried using node for processing a lot of data quickly,…
the blog post is just retarded, you are right
Re: Node.js is good for solving problems I don’t have
#5Exactly, 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 programming these days are few and far between. I haven't worked a job in the last 4 years where no one touched the frontend at some point or vice-versa. Sure, we usually have niches where we do the majority of our work, either front or backend. But at no point are they exclusive.
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. We (frontend folks) live in an asynchronous world. We eat parallel requests, xhr, and async callbacks all day. It turns out that when you apply those same concepts to the server, it opens up a whole new world of possibilities.
Re: Node.js is good for solving problems I don’t have
#6His biggest problem seems to be the "community". There's certainly some people doing projects in node who would probably benefit from doing it with something else. But to judge the framework by some "community" is silly. The node community seems friendly and helpful and have created a large library to help do things node is good at.
Re: Node.js is good for solving problems I don’t have
#7If you don't need node than don't use it, and yes it's not for serving static pages, but more for interactive real-time web applications. And the part where he says that focusing on serving the HTML is less important because it's just 3% of the content seems flawed, because if serving html is slow then the other contents too will be loaded later (the HTML is what requesting them).
Re: Node.js is good for solving problems I don’t have
#8Troll. Post made no sense and came to no conclusion. "The content server should not need to do hardly any IO. Why would an HTML content server need to write to the filesystem?" This just shows a blatant lack of knowledge about what constitues IO. FYI, network is IO, writing to console is IO, logging is IO. The point of an evented system like node (and others based around the 'select' or 'epoll' type calls is that you…
Post also shows a blatant lack of knowledge about what an event loop is. Node and Tornado (two event-loop based servers) are by design single-threaded. This is because for certain setups, having a separate thread for each connected client (the norm for something like Apache) can destroy your server.
IMO the main problem that event loop systems were designed to solve was the "I have a ton of people connected concurrently but the majority of the time these connections are idle". Think if you were building a chat application. Your users are connected to your service constantly (they want to get messages as soon as they arrive), but most of the time they AREN'T receiving or sending data. If you had a thread for every connected client your server would melt due to the ram overhead, even though most threads aren't doing any work 99% of the time. In an event-loop based system, you don't have this issue because everything gets handled by one thread.
Re: Node.js is good for solving problems I don’t have
#9"The problem I have is processing a lot of data quickly"
It seems that the author needs something like super performant Hadoop++. Node doesn't address these problems.
"Node enthusiasts are front-end coders not wanting to do server coding"
I think he missed the point there. Using Javascript as a server side language, node has bridged a gap so many web programmers have been crossing. With node and mongodb, JSON is a language native to the entire webstack -- which is a very powerful idea. We are able to sync datastructures across server and client now.
This rant sounds very similar to "NoSQL DBs will never reach the competence and performance of the RDBMS".
Re: Node.js is good for solving problems I don’t have
#10I was about to extract a few quotes showing a blatant lack of understanding whatsoever. In the end it got too lengthy. Looks like a Ninja stepped on the wrong land today.
All the references to threads are probably the most difficult to understand for me. Node is single threaded and one can't spawn a new one. The author seem to be using it as some sort of magical artefact.. it's beyond comprehension.