I agree completely. For a post-1.0 language, breaking changes should be extremely rare. I think it is fine to add a permanent deprecation notice without ever removing the code, though. In fact, Java's Date class has been deprecated for over a decade, but will probably never be removed. That's the right way to do it: nudge people in the right direction, but don't break their code.
BTW, as [I mentioned in the PR](https://github.com/nim-lang/Nim/pull/14197#issuecomment-644314588), it actually already is a breaking change for code that used `from times import nil`.
