Question about v5 supporting old Node versions
rafaell-lycan opened this issue · comments
Mostly/Probably a silly question regarding Node support, but why keep maintaining old node versions?
AFAIK by dropping the old versions of Node and setting a somewhat newer version like v8 at least would not only take advantage of new features but also allow the framework to reduce a considerable amount of code.
V5 will still require the same good old Node.js 4+ from 2015 and that's the piece I don't process.
As the V5 would be a major release, wouldn't be a good idea to detach that old support in favor of a cleaner code that could potentially make Express faster?
That was something I've been thinking over the past days while testing the V5, I definitely know it's nice to give support for old versions, but I guess it should be a limit of how much should be sacrificed in favor of it.
Anywho, I know for a fact this won't happen soon, but it might be something nice to have in mind on following discussions across the community.
Side note here: My company mostly sticks on the LTS version, and we've upgraded the last services from Node v12 to v16 last year which gave us a nice performance increase overall. I'm wondering how fast Express would be by dropping support to old versions.
Cheers 👋
Hi! Yes, the v5 release has no reason to support old versions, as iterated in other issues :) If there are changes that would reduce code, make it faster, etc., please absolutely feel free to pull request such changes! The only requirement for Node.js support is to support at minimum LTS at the time of the actual v5 release. I hope that helps!