Re:Whytheluckystiff's original domain back as an archive
by shadowgovt on Thursday August 18, 2022 @03:26PM
(#32513818)
For JavaScript, I generally assume backwards-incompatible changes are a non-starter because of its embedding into the browser as its killer app. At this point, we really don't know what websites will break if backwards-incompatible JS changes are made.
Ironically, this has made JS a very stable language (though APIs do occasionally drop out or change drastically for security reasons).
Js (or specifically npm) and python were far slower to adopt this convention, to the point that I think it's fair to say that neither have fully adopted it yet.
Js at least has made almost no backwards incompatible syntax or core lib changes though, which is a point in its favor. Ruby 2 and python 3 were major breaking changes.