Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LTS description #42

Open
jimmywarting opened this issue Aug 24, 2017 · 9 comments
Open

LTS description #42

jimmywarting opened this issue Aug 24, 2017 · 9 comments

Comments

@jimmywarting
Copy link

Just like Nightly, can you also write which node version is the stable, LTS, end-of-support?

skarmavbild 2017-08-24 kl 14 33 02

@williamkapke
Copy link
Owner

Hey- that's a decent idea! 🤔 I'm swamped right now so I'll leave this open as a TODO. Maybe a PR will come in!

@piranna
Copy link

piranna commented Feb 5, 2020

It would be nice to have an option to show only maintained versions, too. Nobody should be worrying for something older than Node.js 8.x anyway... :-)

@ljharb
Copy link
Collaborator

ljharb commented Feb 5, 2020

I support down to 0.4; it's a fine checkbox to add, but there are plenty of very good reasons to not leave users stuck on unmaintained node versions in the lurch.

@piranna
Copy link

piranna commented Feb 5, 2020

there are plenty of very good reasons to not leave users stuck on unmaintained node versions in the lurch

Could you be able to tell me some of them, please?

@ljharb
Copy link
Collaborator

ljharb commented Feb 5, 2020

When someone is on, say, node 4, and wants to upgrade to node 10, that's a risky and costly effort. The best way to derisk it, and make it cheaper/faster, is to first upgrade all deps while still on node 4, which hopefully all work on both node 4 and node 10, and then upgrade the platform after tests are passing. Every dependency that requires updating it at the same time as updating the platform makes the platform upgrade harder, and thus can prevent it from happening at all. Supporting old platforms makes it easier for people to upgrade, not harder.

@piranna
Copy link

piranna commented Feb 5, 2020

Fair enought, but here is not about Node.js deprecations, but instead about new EcmaScript functionality available in newer versions of Node.js, and they are backwards compatible. You are right about maintaining documentation of Node.js APIs, and I agree about having a checkbox to show the unmaintained versions, just only having it enable by default to show all versions is superfluous.

@ljharb
Copy link
Collaborator

ljharb commented Feb 5, 2020

Indeed; I was responding to

Nobody should be worrying for something older than Node.js 8.x anyway... :-)

@piranna
Copy link

piranna commented Feb 5, 2020

Oh, sure, but in that case, it's responsability of the developer to have it's project dependencies and environment updated without waiting until It gets unmaintained and deprecated... :-/

@ljharb
Copy link
Collaborator

ljharb commented Feb 5, 2020

It's also their prerogative to keep using something even if its maintainers have abandoned it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants