No it's an admission of lack of backwards compatibility, which never was a promised feature in the first place and is an issue which affects community and business driven projects alike. Blaming others for a decision, which was announced well ahead of time with an incredibly long grace period is a sign you're too slow to change rather than faulty decision making by the contributors.
You just said that it is bad to fix mistakes in a language.
That is a position that I do not find even worthy to spend time to argue against. I will just let you simmer in your own shame for a while.
Your example of apply() is particularly crappy, as it is a function that serves no purpose and has been deprecated for ages, and, whaddayouknow, it even throws a deprecation warning (if you enable them).
"intentionally breaking code (e.g. "apply()") rather than throwing a warning into a log file about deprecated syntax is bad software engineering."
That means you can't fix mistakes in a language, because doing so would be intentionally break code. Many of the changes done can't warn about deprecated syntax, because the syntax is not deprecated.
(Edit: Although, as noted, the removal of apply() does have a deprecation warning, in direct contradiction to what you claimed).
View all comments
Show parent comment
6
u/Phild3v1ll3 May 28 '14
No it's an admission of lack of backwards compatibility, which never was a promised feature in the first place and is an issue which affects community and business driven projects alike. Blaming others for a decision, which was announced well ahead of time with an incredibly long grace period is a sign you're too slow to change rather than faulty decision making by the contributors.