This has been discussed a great deal the first time such a decision had to
be made.

If anything has changed since, is that we have more packages following the
convention established by the FIG than before.

I personally follow this convention, and a lot of member projects (probably
the majority, cba to check) do too and, while I understand the reasons of
those who don't like it, to be honest I find such bike shedding almost
close to a tabs vs spaces debate, as in: we'll never have a strong majority
on either side.

In my humble opinion, once a convention is in place, the consistency
argument is much harder to argue against and this fact alone is enough to
dismiss the proposal.

Il giorno mer 17 ago 2016 alle ore 22:21 Márk Sági-Kazár <
mark.sagika...@gmail.com> ha scritto:

> Hi all,
>
> Huge +1, here is why:
>
>
> > When you call ResponseInterface and Response how do you understand
> whether it is a concrete implementation or not.
>
> You don't, and if you do, you are doing it wrong.
>
> Your code doesn't care whether it requires an interface to be implemented
> or an actual object, because it receives an INSTANCE of the type.
>
> Classic example: do you have a car, a Ferrari or a FerrariCar?
>
> car: object
> Ferrari: type
> FerrariCar: bad name
>
> Regards,
> Mark
>
>
> 2016. augusztus 15., hétfő 21:53:26 UTC+2 időpontban Matthieu Napoli a
> következőt írta:
>>
>> Hi all,
>>
>> This is a 2 weeks discussion before going to a vote.
>>
>> The "Interface" suffix has been questioned a few times already, I'm
>> suggesting we put that up to a vote and avoid future debates. Here are
>> relevant threads I could find on the topic:
>>
>> - https://groups.google.com/d/topic/php-fig/Zgfd0gHUUoc/discussion
>> - https://groups.google.com/d/topic/php-fig/dPwtKqO3Zqk/discussion
>> - https://groups.google.com/d/topic/php-fig/10lM-UNudvU/discussion
>> - https://groups.google.com/d/topic/php-fig/aBUPKfTwyHo/discussion
>>
>> Suggested change: *replace "MUST" to "MUST NOT" in "Interfaces MUST be
>> suffixed by Interface"* from
>> http://www.php-fig.org/bylaws/psr-naming-conventions/
>>
>> I do not suggest accepted PSRs are changed.
>>
>> Please share your reasons to vote FOR or AGAINST the change, let's debate
>> for 2 weeks or more, and then let's have a vote to settle this.
>>
>> Discussion will last for at least 2 weeks (20:40 UTC on 29 August 2016).
>>
>> ---
>>
>> Here are my arguments to vote FOR the change:
>>
>> *- the Interface suffix makes simple names very long*
>>
>> For example with PSR-7, here is the signature of a Slim/Zend Expressive
>> middleware:
>>
>> public function __invoke(ServerRequestInterface $request, ResponseInterface 
>> $response, callable $next) : ResponseInterface
>>
>> {
>>
>> }
>>
>>
>> Compare that to:
>>
>> public function __invoke(ServerRequest $request, Response $response, 
>> callable $next) : Response
>>
>> {
>>
>> }
>>
>>
>> The last one is much simpler and clearer. Typing and reading the first
>> one is a huge pain. This point applies of course to all PSRs, not just
>> PSR-7.
>>
>> *- the Interface suffix makes the interface a detail and the
>> implementation the main thing, it should be the other way around*
>>
>> We should care about the interface, not the implementation. Type-hinting
>> against LoggerInterface means that "Logger" (the implementation) is still "
>> *the* logger", and the interface is a secondary concept that we
>> explicitly inject for decoupling.
>> If "Logger" was the interface, it would be even more obvious that the
>> interface is the most important part. The implementation is secondary and I
>> don't even care how it's named. I just want a logger and that's what the
>> interface is.
>>
>> Regarding the inconsistency it would create between PSRs I think it's
>> nothing compared to what we would gain in terms of developer experience.
>>
>> Matthieu
>>
>

-- 
You received this message because you are subscribed to the Google Groups "PHP 
Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to php-fig+unsubscr...@googlegroups.com.
To post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/CAFojS1uQCYJiEWfPYvBqh3JaKWCr8w-ost5NHF8HQKozveviog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to