Le mercredi 8 avril 2020, 07:35:10 CEST Paul M. Jones a écrit : > ## Lessons Learned > > ### Userland Functionality > > The initial impression is that there is a strong desire for work that *can* > be done in userland to *stay* in userland. However, that impression conflicts > with the recent acceptance of `str_contains()`, which is very easily done in > userland. > > **Lesson:** Of functionality that can be accomplished in userland, only > trivial/simple functionality is acceptable.
My take on that is more that functionality in core needs to be «perfect», or at least near unanimous. And of course it’s way easier to find a solution which pleases everyone when it’s for something quite simple. I do think OO interface for request/response in core is something that could pass, but it would need to be more in line with what people want/expect. > ### Userland Ecosystem > > There was somewhat less concern for "the ecosystem," but it too was prevalent > in the discussion. > > **Lesson:** Perceived challenges to popular userland projects are going to be > met with strong resistance by their existing stakeholders, even when an RFC > is explicitly not a challenge to them. You clearly disagree on this with most participants in the discussion, but saying «this RFC is not a challenge» is not enough to make it true, there was a clear overlap of feature between your RFC and existing userland projects so it made sense to compare them. -- Côme Chilliet FusionDirectory - https://www.fusiondirectory.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
