3 ms·
It feels like the problem is the black-and-white thinking on the part of developers of every language being either "okay to develop in" or "completely unsupport
by derefr 13y ago
It feels like the problem is the black-and-white thinking on the part of developers of every language being either "okay to develop in" or "completely unsupported."
If only there was a way to deprecate a language, with the same meaning as deprecating an API method: "it's not gone yet, but it will be soon, so in strict mode using it is an error." (The main problem to solve would be: strict mode of what? The package manager?)
- al2o3cr 13y ago"If only there was a way to deprecate a language, with the same meaning as deprecating an API method" One way that usually works is to release a newer version and stop updating the old one after five years. Oh wait...
- derefr 13y agoIt's the "using it in strict mode is an error" part that's important. Compilers can automatically refuse to compile deprecated-but-not-broken code. What can automatically refuse to let you start a new project in a deprecated-but-not-broken language?