> 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 source code predates the PHP 3 days, but that's just one of the > problems. 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 — of course, if needed, we can discuss this in more detail later. > > 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 > for building websites?
Interesting? Maybe. A good idea? Definitely not. If there’s one rule in refactoring, it’s that you never do ground-up rewrites of something which works. They always go badly. If there are problems, you can refactor. There is no need for a rewrite. -- Andrea Faulds http://ajf.me/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
