+1 Many people have already very clearly stated the legitimate issues with having an "Interface suffix" standard; how you've overlooked these is mind boggling. The only objective support given so far to keep this standard, is so that some developers can know whether or not they are looking at an Interface or a concrete class while coding. This is not a valid argument, because if you are using interfaces then this distinction is entirely useless to the developer.
As a developer, having to type out Interface all over the place is highly annoying and redundant. It introduces noise for no tangible benefit. Same can be said for Trait or Abstract, but Interface is more common. It also encourages poor naming habits, as developers end up using generic names for classes that would otherwise *have to be* an implementation-specific name, simply because the 'default' name has not yet been taken. Developers are lazy and will always try to get away with doing the minimum amount of work. And I mean that in a both a good and bad way. I agree with all of the points that @Daniel Plainview has made so far. On Monday, August 22, 2016 at 6:39:48 PM UTC-4, Damian Mooyman wrote: > > I would add to this that given the goal to provide a standard pattern, in > the absence of legitimate issues with pre-existing standards, the status > quo should prevail. The consistency and rigidity of the standard is a lot > more important than what the standard actually prescribes. > > > > On Thursday, 18 August 2016 12:08:12 UTC+12, Woody Gilk wrote: >> >> >> On Wed, Aug 17, 2016 at 4:53 PM, Roman Tsjupa <draco...@gmail.com> wrote: >> >>> It is not about being right or wrong really. Its more about being strict >>> for no good reason. Its a backwards compatible change, so if you like you >>> can still suffix your interfaces. >>> >>> >> Roman, the reason FIG exists is that it takes personal choice out of the >> matter and thereby provides consistency. This proposal does neither. >> >> -- >> Woody Gilk >> http://about.me/shadowhand >> > -- 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/5ea268cc-7ec0-486a-948e-69f0fe631156%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
