mic_none

Talk:Node.js Source: en.wikipedia.org/wiki/Talk:Node.js

"Its development and maintenance is sponsored by Joyent"

[edit]

The citation for this points at http://www.sdtimes.com/content/article.aspx?ArticleID=35668&page=1, but the referenced page makes no absolutely no statements to that effect, at all.

http://nodejs.org/ does state "the node.js project is sponsored by Joyent", it would make a better citation.

However, uncritical acceptance of this as fact, without at least a statement of what "sponsor" means, makes this page more of an advert than a useful statement about who develops node.

Better would be the following page:

https://github.com/joyent/nodehttps://demo.azizisearch.com/lite/wikipedia/page/Project-Organization

Which shows that a number of companies are sponsoring Node.js development (by paying the core developers). That page is out-of-date, Ben Noordhuis was removed from the team by Joyent, and Isaac Schlueter is now an employee of Npm Inc.

Listing the 500+line Node AUTHORS file as the "Developers" doesn't reflect who the Core developers are as well as the Project's wiki page: https://github.com/joyent/nodehttps://demo.azizisearch.com/lite/wikipedia/page/Project-Organization

Where is the event loop?

[edit]

Much of the technical part of the article explains the event loop, but does not make it clear where this event loop is executing. Is there one event loop per client, running on each client computer? Or is there one event loop per created server? Or is it a virtual concept without actual existence? It is obvious that it cannot be located in a single cloud-based supervisor server, for that would be a single point of failure and would prevent scaling up. If anyone knows the answer, please add it here or to the article, and thanks. Also, as a long-time Windows programmer, I am aware that Windows is based on an event-driven mechanism sometimes called the Message Pump, rather than on process and thread switching (which are also implemented in Windows, but are not so central to its programming). Does the nodejs event loop work like the Message Pump, handling event messages? Or does it interact in some way with nodejs asynchronous callbacks? David Spector (talk) 12:54, 12 August 2018 (UTC)[reply]

Older versions

[edit]

Why does the article say that Node was first created in 2009, and even Microsoft got involved in 2011, but the first version was released in 2013? 2601:181:C380:5A40:8DB7:53F2:3337:13A2 (talk) 03:29, 21 December 2021 (UTC)[reply]

Color coding of versions?

[edit]

The CURRENT version is listed as 23.x, and as such its cell color is green. But it is recommended that most people use LTS versions (even-numbered versions). Might it be smarter/safer to have ACTIVE and MAINTENANCE version cells colored green which is aligned to "safe to use", and have CURRENT version be colored yellow ("use with caution")? Developers who should be using a CURRENT release will know they should. Developers and users who should be using an LTS version might not know, and might grab CURRENT because "it is green". — Preceding unsigned comment added by Wiki.gregfenton (talk • contribs) 02:31, 25 May 2025 (UTC)[reply]

@Wiki.gregfenton: I think you're on to something. We should indeed mark the Active LTS as the latest stable (green), as that reflects how Node.js sees itself. The download page even defaults to the Active LTS, with note to only try the latest version for new features.
The legend and color swatches in the release tables on Wikipedia are actually standardised across articles, where the colors have specific meanings. The yellow is applied to versions designated as "C-O", for "Current Old". This would be inaccurate for the Node.js "current" releases, as those are not older than the LTS. Likewise, the "Maintenance LTS" should not be latest stable (green) but remain yellow as-is, since it is indeed a "current but older and still supported" version.
One additional piece of information here is that the status of a Node.js version changes over time. The most obvious changes are that an "Active LTS" eventually becomes "Maintenance LTS", and all releases eventually become End-of-life. A less obvious change is that an LTS release actually starts as a "Current" release in April/May and then becomes the "Active LTS" six months later in October (e.g. Node.js v20 announcement, Node.js 24 announcement).
I've done the following in my edit:
  • Change "Current" from latest stable (green) to latest preview (blue). This preset was previously disabled on this article.
  • Change "Active LTS" from current old (yellow) to latest stable (green).
  • Keep "Maintenance LTS" as current old (yellow).
Krinkle (talk) 23:40, 22 June 2025 (UTC)[reply]