5 ms·
Err... isn't the whole point of a big number release to introduce big, breaking changes? All major projects have breaking changes... but only the nice ones do u
by chaorace 2y ago
Err... isn't the whole point of a big number release to introduce big, breaking changes? All major projects have breaking changes... but only the nice ones do us the courtesy of saving breaking changes for major release milestones
- DEADMINCE 2y ago> Err... isn't the whole point of a big number release to introduce big, breaking changes? Certainly not. Breaking changes should still be avoided as much as possible.
- chaorace 2y agoSo are you saying that now was not the time for a major release? Or are you saying that the major release had too many breaking changes?
- hesviiggvv 2y agoOption C: They were dumb breaking changes.
- 8n4vidtmkvmk 2y agoProbably not. 9 is a big number. They're probably breaking too often. Should only break every few years.
- winrid 2y agoEslint released in 2013, so sounds about right. Even Java has had more major releases than that.
- erhaetherth 2y agoDataTables released in about 2008 (https://cdn.datatables.net/1.0.0/js/jquery.dataTables.js https://cdn.datatables.net/1.0.0/js/jquery.dataTables.js) and just released 2.0 on Feb 15 this year (https://cdn.datatables.net/2.0.0/ https://cdn.datatables.net/2.0.0/). No BC-breaks that I'm aware of in 16 years. Not saying every project can do it, but some of these ESLint changes seem rather unnecessary. React always adds warnings in 1 major release and then removes in the following major release, meaning if you have no warnings you can just upgrade without fear, which is quite a nice way of doing it.
- winrid 2y agooh man, datatables, that takes me back. I agree that the way React does things is preferable.