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 already,
Good evening, Internals!
*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 especially because I think
it's part of the PHP environment, just like the spec
I'm not go further into the details of the problems we actually
have inside that code, as they are very obvious and the source code speaks
for itself
I'm all for having a discussion about updating the website. But on the
flip side of that token, you can't just drive by here, suggest a
On 24 Oct 2014, at 19:52, Daniel Ribeiro drgom...@gmail.com wrote:
You all know the http://php.net website and it's source code
https://github.com/php/web-php. It comes to my attention that this source
code is pretty much a very good example of how *not *to build websites in
PHP — the
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 especially because I think
it's part of the PHP environment,
On 25 October 2014 03:15, Rowan Collins rowan.coll...@gmail.com 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
What I wanted to know from you is: would it be interesting if we started a
complete rewrite of the website, not only for actually improving it, but
also for making it serve as a reference for people to see how the PHP
environment has evolved and what are the good practices we use these days
