Talk:Node.js
WikiProject Computing | (Rated Start-class, Low-importance) | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Contents |
Intro needed
If the reader is not a Javascript programmer, this article does not tell them (i.e., me) anything useful at all about Node, what it is or what it does. The code snippets are only useful for people who already know about this field. Liam Proven (talk) 13:50, 2 March 2011 (UTC)
- True. I tried to make the lede somewhat more understandable in a recent edit, but it requires non-programmer readers to click on wikilinks. If anyone wants to expand on my work, please go for it. Cheers, CWC 08:43, 30 November 2011 (UTC)
NPM
Should the article mention the Node Package Manager (NPM)? It seems to have won the "package manager war" for node.js and seems to be far more popular and active than its competitors or JSAN (which the CPAN article mentions as the JavaScript package manager). -- 78.35.115.245 (talk) 10:50, 1 March 2011 (UTC)
Node History
This article has some nice info on node and its history. Can be used to expand the article.--175.136.62.233 (talk) 19:25, 11 September 2011 (UTC)
- Good one, thanks. I've just added to the article as a source for an existing statement, but we should use it more widely. Cheers, CWC 08:43, 30 November 2011 (UTC)
asynchronous i/o
i think this needs a discussion on asynchronous i/o, and an explanation of the difference between asynchronous-io/web-workers and threading/concurrency (as i understand it, asynchronous i/o, especially for server i/o, is a crucial use of of node.JS). perhaps also we can discuss why people have see node (especially in the context of server-scripting with asynchronous solutions) as providing a performance/scaling advantage (despite the performance compromised by the use of a high-level interpreted language, JS). also along the lines of performance, maybe this article also needs more thorough discussion of the google V8 engine for JS rather than just a mention and link? 50.74.192.11 (talk) 15:22, 4 October 2011 (UTC)
- Yeah, async I/O is a core feature. The article now has links to relevant Wikipedia articles, which helps, but a proper explanation would be better. CWC 08:43, 30 November 2011 (UTC)
Need better sources, fewer External links
User:Thumperward recently tagged the article with {{advert}} and {{selfpublished}}. I've changed those to {{External links}} and {{refimprove}}, but his point still holds: the sources cited in the article tend to be written by fans of Node.js, and the external links section is too long. I should be doing other things, so I'm not going to tackle this myself. Can anyone else help out?
The problem we face is that lots of people are very enthusiastic about Node.js (for good reason, IMO), and articles about it tend to be more enthusiastic than desirable in a good source for an encyclopedia. So we have to be more careful about selecting the sources to cite than in most computing-related Wikipedia articles. Cheers, CWC 08:45, 30 November 2011 (UTC)