On Sun, 28 Jul 2019 at 20:21, Stanislav Malyshev <smalys...@gmail.com> wrote: > > Did you actually try to read my argument, of just > decided to strawman it from the start?
I strongly doubt that there is anything that people could say that would alleviate your concern. I could say how nicely my IDE gives me a warning when I edit files from a library that don't belong to the project. I could point to how the Javascript community are deliberately going out of their way to make it easier to 'fracture' the language, by using pre-compilers, and they have used that to drive evolution in the JS ecosystem.* But from previous RFC discussions, you only want to discuss possible concerns; not in an attempt to try to make the RFC better, or to come up with a better idea, but to just put pressure onto the RFC author to withdraw the RFC. The suggestion that RFC authors need to win you over in a discussion, otherwise they aren't doing their job properly appears to be another level of trying to shout down RFCs by making life less pleasant for those RFC authors. While it's admirable that you are strong in your beliefs, it is incredibly tiring engaging in RFC discussions with you, when so often don't it seems to be a waste of time, due to there being nothing that could be said that would change your mind. You can't expect people to respond to all of your points, when it doesn't seem to be a useful use of their time. cheers Dan Ack * And that the PHP community will have an easier time than JS devs do, as PHP devs are completely in control of the computer where their code will run, but JS devs have to run their code in a browser which they have no control over. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
