On Fri, Nov 29, 2019 at 9:48 PM Abdur-Rahmaan Janhangeer firstname.lastname@example.org wrote:
One of them can maybe be deprectated
Deprecation is not a solution. You're still going to have stuff out there using the old name (Stack Overflow posts, blogs, articles, books, etc etc etc etc), and people *will* have to learn the meaning of both. Additionally, churn like this - renaming things for no reason other than "the new name is somehow better" - tends to create the sense that the language is constantly in flux, and that today's code is going to be broken tomorrow. Imagine a Stack Overflow answer that has to be edited to say "For Python versions up to 3.8, use json.loads; for versions 3.9 and up, use json.load_string", and then if it uses a couple of other APIs that have been renamed, it needs to multiply that out exponentially... no thanks. I get enough of that from React.js.
-1 on renaming. -1 on deprecating. -1 on creating an unnecessary alias.