On 25/10/14 17:24, Levi Morrison wrote:
> The reason I bring this up in this discussion is that switching to
> something like Polymer is going to require a few changes on how we
> generate the HTML and CSS. The the best time to refactor code is when
> you are already changing it for something alrea
>> Meanwhile, I agree with both Kris and Andrea's responses: you need to be
>> specific about what problems you propose to fix, and you need to be
>> extremely wary of breaking existing functionality just because it's
>> "interesting" or "modern".
>
> +1.
>
> There are also a lot of technological c
On 25 October 2014 03:15, Rowan Collins wrote:
> Daniel Ribeiro wrote on 24/10/2014 19:52:
>>
>> *Disclaimer: *I wanted to bring this discussion inside the internals
>> mailing list not only because of the fact that the PHP.net website's
>> source
>> code on GitHub doesn't have issues enabled, but
