News for hackers. Stuff that matters.

A comment on JavaScript frameworks and topics to learn in 2017. Parent comment

Re:JavaScript frameworks and topics to learn in 2017 by jessaustin on Monday December 19, 2016 @11:47AM (#13212685)
That's great, but it ain't there yet. [0] Incidentally, releasing a version 2 without deprecating version 1 seems a bit of a project smell... It might be the right thing to do in a particular situation, but what happened on the project that led to that situation?

[0] Tree shaking completely broken? #2867 https://github.com/webpack/webpack/issues/2867

[ Parent | on HN ]
Re:JavaScript frameworks and topics to learn in 2017 by prodigal_erik on Monday December 19, 2016 @08:47PM (#13216670)
Whole versions don't get deprecated. Visible features get deprecated when they are still present in the latest version but will be missing or incompatible in the next major version.
[ Parent | on HN ]
Re:JavaScript frameworks and topics to learn in 2017 by jdd on Monday December 19, 2016 @02:39PM (#13214349)
Not smell just semver – http://semver.org/
[ Parent | on HN ]
Re:JavaScript frameworks and topics to learn in 2017 by jessaustin on Monday December 19, 2016 @08:12PM (#13216510)
To my mind, the "semver way" would be to make tree-shaking an option on a new minor version. After some number of releases, it might become a default on a new major version, if the maintainers so chose. Splitting the project into multiple codebases is not required by semver.
[ Parent | on HN ]