Functions like php7_htmlspecialchars() wouldn't live in the standard library, they would live in the "compatibility library" instead. That might help discourage new users from using them and mentioning them in tutorials.
I agree with your point that bulletproof conversion will make reflection-heavy code less readable. But still, if we can make a bulletproof converter that works on 100% of old code and leaves simple code relatively unchanged, doesn't that open up some nice options for everyone?
- Users who don't care about code quality, and just want their old code to work, will be happy because they will have a push-button upgrade solution.
- Users who care about code quality will also be happy, because they can run the converter and have a complete working program right away. Afterwards they can modernize it piece by piece, at their own pace, having a complete working program at each step. Without the converter they'd be stuck doing a full rewrite.
- Language implementors will be happy because they can keep the language clean as it evolves. Imagine how awesome Java could be today if they took this route.
I agree with your point that bulletproof conversion will make reflection-heavy code less readable. But still, if we can make a bulletproof converter that works on 100% of old code and leaves simple code relatively unchanged, doesn't that open up some nice options for everyone?
- Users who don't care about code quality, and just want their old code to work, will be happy because they will have a push-button upgrade solution.
- Users who care about code quality will also be happy, because they can run the converter and have a complete working program right away. Afterwards they can modernize it piece by piece, at their own pace, having a complete working program at each step. Without the converter they'd be stuck doing a full rewrite.
- Language implementors will be happy because they can keep the language clean as it evolves. Imagine how awesome Java could be today if they took this route.