[deleted]
Node.js is good for solving problems I don’t have
21–30 of 61 posts
Re: Node.js is good for solving problems I don’t have
#22The 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.
Re: Node.js is good for solving problems I don’t have
#23"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 la…
You have solved a problem that didn't exist -- XML and HTML were both reasonable linguafrancas prior to JSON's invention. JavaScript as a server-side langauge is not a good thing; JavaScript is not a good systems language. We've already had an era of a poor systems language (PHP) being predominant in the web application space, and the conclusion was that there are better languages which can more effectively represent…
- XML and HTML are good ways to structure data...sometimes. Other times, they're godawful. Especially if you're trying to pass data from one piece of code to another piece of code in order to do RPC-like things (server->client, for example). There's a reason that JSON is popular, and it's not because "it's the cool thing to do".
- JSON is a strict subset of Javascript syntax. You can always eval() a JSON string to convert it (not that you should). Many browsers support native JSON parsing now, so it's also very fast. I'm not sure what the downside is there.
Re: Node.js is good for solving problems I don’t have
#24Exactly, 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…
"""Exactly, 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."""
You'd be surprised how many people take the wrong answer, then. I've seen tons of posts touting Node from people with needs and problems that would be better served by other technologies.
"""Node makes it possible to do completely new things that would be difficult to do otherwise."""
Really? Like what? Besides running server side js (something that Netscape did back in the mid-nineties), Node offers nothing that one of the tons of evented servers/libs around could not previously handle. .
I personally like the Mongrel2 approach --combined with some non-blocking framework you got all the Node goodness, plus traditional server goodness, plus messaging, plus language agnosticity.
Re: Node.js is good for solving problems I don’t have
#25"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 la…
"""This rant sounds very similar to "NoSQL DBs will never reach the competence and performance of the RDBMS"."""
Well, performance wise NoSQL DBs are faster. In anybody doubting that?
As for the competence part, well SQL DBs (by which I don't mean MySQL) are based on a little something called Relational Algebra. Which is math. Which is a (formally) proven and coherent set of methods for data representation and querying.
NoSQL DBs are just ad hoc solutions.
Not the same thing.
Re: Node.js is good for solving problems I don’t have
#26Exactly, 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.
Re: Node.js is good for solving problems I don’t have
#27Earlier quoted context omitted.
You have solved a problem that didn't exist -- XML and HTML were both reasonable linguafrancas prior to JSON's invention. JavaScript as a server-side langauge is not a good thing; JavaScript is not a good systems language. We've already had an era of a poor systems language (PHP) being predominant in the web application space, and the conclusion was that there are better languages which can more effectively represent…
Regarding Javascript, I think it suits well the async paradigm because that's how people expect Javascript to be. Why isn't Javascript a good server-side language?
I agree that js does support the async paradigm for the reason you mentioned; however, at the risk of sounding like I'm speaking for the op js would not be my first choice for system or server side programming. The simple reason being that javascript's behavior is often near inexplicable, many examples can be found here: http://wtfjs.com. I'm tolerant of that strangeness while manipulating the DOM but really only because there are no other choices.
Re: Node.js is good for solving problems I don’t have
#28Node was created to provide an event-based web server programming model
This is not true, and it's probably why the author seems confused. Node was not primarily designed to be a web server, nor is it particularly good at that. It is much better as a server that keeps sockets open, like for a chat application.
Re: Node.js is good for solving problems I don’t have
#29Someone should tell the Nginx guys that blocking IO is not a problem that web servers actually have. I'm sure they will be thrilled to not have to do complicated event programming anymore.
Re: Node.js is good for solving problems I don’t have
#30Exactly, 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 already do that. If I need to write a more traditional kind of page, I use Django and Python. Easy to setup, excellent framework and language to work with.
I use node for new cutting edge things which Django and Python can handle, but not as easily as node.