Hacker News new | ask | show | jobs
by arshbot 2584 days ago
But in reality, you can't ( and shouldn't ) go back and change how the rest of the legacy codebase does things just because there's a new way to do it.
1 comments

Right - They tried dropping legacy compatibility before, and people are still upset 10+ years later.

For something as essential as strings, it makes sense to recommend the "new" way, and continue to support the "old" way.