You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node.js 4.x goes out of life in little over a month. How do we feel about dropping support for that version (and 5.x) in Canvas 2.0?
I think it could be a good idea to get this in before releasing 2.0, since we otherwise need to support Node 4.x for the entire lifespan of 2.x. This might not seem problematic right now, but might be in the future as Node moves forward.
It seems like people have been better moving away from Node.js 4.x than they were with 0.x. When 0.10 went EOL it had an 11% market share. When 0.12 went EOL it had a 5% market share. Version 4.x currently holds at 7%.
Node.js 4.x goes out of life in little over a month. How do we feel about dropping support for that version (and 5.x) in Canvas 2.0?
I think it could be a good idea to get this in before releasing 2.0, since we otherwise need to support Node 4.x for the entire lifespan of 2.x. This might not seem problematic right now, but might be in the future as Node moves forward.
It seems like people have been better moving away from Node.js 4.x than they were with 0.x. When 0.10 went EOL it had an 11% market share. When 0.12 went EOL it had a 5% market share. Version 4.x currently holds at 7%.
ref: node market share, node versions
ping @zbjornson @chearon
The text was updated successfully, but these errors were encountered: