4 ms·
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.
by arshbot 7y 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.
- e1ven 7y agoRight - 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.