Re: Namespaces internal refactoring
| From: | Marco Pivetta | Date: | Sun, 14 Aug 2016 22:40:56 +0000 |
| Subject: | Re: Namespaces internal refactoring | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95155@lists.php.net to get a copy of this message | ||
Hey Stas
On 15 Aug 2016 00:35, "Stanislav Malyshev" <smalyshev@gmail.com> wrote:
>
> Hi!
>
> > A realization that needs to be made is that beginners would be using
> > libraries that requires to make valid restrictions, preventing those
> > beginners to mess up with code they shouldn't. So even if the use case
> > is only valid for 0.01% of code producers, it might be valid for 20%+ of
> > consumers.
>
> I don't think PHP needs more bondage-and-discipline. If beginners "mess
> up with code they shouldn't" that is usually, in my experience, a sign
> of library authors not serving their use case well, and not implementing
> functionality that they need. Either because they didn't know, or
> because their opinion about user's needs differs from user's opinion
> about their needs. In this case, I'm on the user's side. Hacker's ethos
> is doing things other people think can't be done.
*You* don't think so, but this happened many times also with non-beginners
(what Guilherme was talking about).
Conventions are not sufficient to keep a codebase consistent and safe:
explicit rules do that.