31 Aug
2014
31 Aug
'14
1:38 p.m.
On Sun, Aug 31, 2014 at 5:47 PM, Gregory Collins
Only if we run a deprecation cycle for at least one major version of network. Just removing a function breaks code for no reason and is user-hostile. It's important to give end users a warning that the function is going away and some time (12 months or more IMO) to fix their code, especially for packages that belong to the platform.
I like Java's policy of only deprecating (and often never removing) functions that are actually dangerous to use (i.e. easy to use incorrectly.)