Been informed I missed a candidate from my ballot, apologies for the double
post.
I'd like to ammend my ballot to place Lukas after Korvin.
Regards,
Andrew
--
You received this message because you are subscribed to the Google Groups "PHP
Framework Interoperability Group" group.
To unsubscrib
Hi all,
*Short Reminder:* Voting only for your buddies and voting without doing
research is how we got into this mess in the first place. It's exactly the
problem we're trying to fix. If you can't spend half an hour checking out
the candidates and their background - your vote is more damaging t
m lib developers as they can anyway not rely
> on any guarantee from the cache.
>
> Does this make sense to you?
>
> Cheers,
> Jordi
>
> On 17/11/2016 18:43, Andrew Carter wrote:
> > Not sure I fully understand that - as a user I can't rely on common
> >
nt' researched in depth.
>
> As such I am ok leaving it as is because the common-sense
> implementations will do it right, and it doesn't warrant breaking away
> from PSR-6 IMO.
>
> Cheers
>
> [1]
>
> https://symfony.com/doc/current/components/cache/cach
Sorry for the double post, what's the reasoning behind returning a boolean
if the set() operation fails? I'd naturally expect that to be an exception
(it's not the same as a cache miss, there must have been some error).
On Wednesday, November 16, 2016 at 2:22:20 PM UTC, Jordi Boggiano wrote:
>
>
Good work.
One thing that always bothered me from a user perspective was not being
able to put an item in the cache that doesn't expire (different from a
default expiration time). Having to create times really far in advance is
messy, and you never know if you're going to run into 2038 bugs etc
Some projects still don't use PSR-2 because of the hell involved in changing
style guide mid project when you have hundreds of pull requests. PSR-2 didn't
have the option of being prescriptive.
The job of the FIG is to solve problems by working together?
These projects are the community, so if
The objection to being prespective rather than descriptive makes absolutely
no sense - and I couldn't disagree any more.
All of the projects in this group writing PHP 7 code will (hopefully) *need
to develop their own style guide anyway* - save the work, and create one
together now.
Don't wait
They use "callable $next" and they have a different structure (double pass).
It makes even more sense to have type safety if we're introducing a
different middleware signature that's different to one that's commonly used
in the wild. This would prevent incompatible middleware from being
acciden
Type safety, IDE type hinting.
A callable can be anything, an interface guarantees parameter types and, in
PHP 7, return types.
Interfaces also indicate explicit implementation of the standard - rather
than implicit implementation on the basis that the passed parameter could
be executed.
All
In general, my response to these comments are that you could make similar
arguments for basically any PHP software component. If the FIG was to
standardise every aspect of framework development, we would end up with a
FIG framework that was no different from the others and actually worked
again
d interface for them
>
> On Thu, Jul 7, 2016 at 10:35 AM, Andrew Carter > wrote:
>
>> I don't see this as an area where interoperability is better than
>> innovation, but I could be persuaded. I think the FIG has to be careful not
>> to standardise things for the s
I don't see this as an area where interoperability is better than
innovation, but I could be persuaded. I think the FIG has to be careful not
to standardise things for the sake of it - because it could be done - but
rather because it would be beneficial to the ecosystem to do so.
Composer alrea
disagree with the point of
view that was suggested (that Dracony should no longer be a voting member).
Last post from me as I'm aware of unwritten self throttling rules.
On Thursday, July 7, 2016 at 3:51:58 AM UTC+1, Matthew Weier O'Phinney
wrote:
>
>
> On Jul 6, 2016 6:40 PM, &qu
>
> My main point of contention is that I feel Paul argues legalities only
> when he disagrees with outcomes, which, in the past six months, seems
> to be essentially every decision, judgment call, etc.
>
I disagree - Paul would have voted to expel Dracony but voted against the
motion because
15 matches
Mail list logo
