Den tir. 16. jun. 2020 kl. 02.39 skrev Daniel Rodrigues Lima <danielrodrigues...@hotmail.com>: > > The simple fact that we don't know how to deal with this type of discussion > can say a lot about of our community. > Anyway when I started this discussion I didn't imagine that I would receive > so many negative feedbacks.
I am sorry but I don't think you fully understand the implications it may have. I get it, there is no easy answer but while the change may be simple and elegant to rename a few places you may find problematic, you have to understand the consequence of the users it has and what statement it means the PHP project as a whole is sending. If we openly change these names without further, we also declare open season for changing anything anyone may find offensive in whatever way that may be in the language. It sends a strong signal to our users that reliable backwards compatibility policies we have inplace, which our users enjoy, may no longer be as reliable. This puts a greater burden on upgrading from one PHP version to another, if your time is just spent on search, replace and test for things like these. I mean personally I would much rather solve interesting problems and I do not find censoring words like blacklist into blocklist to be an interesting problem to solve, because I do not see it as a problem in the first place (either in my professional world, personally or as a PHP Core Developer). Right now you threw the ball in the air without looking and you seem amazed where it landed. -- regards, Kalle Sommer Nielsen ka...@php.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
