>> 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.
Agreed: don't rewrite from scratch. I think our HTML/CSS is in need of a lift once browser adoption is better for some of the more recent improvements. Using something like Polymer for our front-end would drastically simplify the code and significantly improve the user experience. I've already done a port on my local copy and it works pretty nicely. However, I don't think Polymer is fully stable yet and I don't think we're ready to ditch IE 9 either. I haven't said anything on list about this because the browser adoption rates need to improve and Polymer (and other similar projects) need to stabilize. 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, so it would be better to delay refactoring code until we have some need to change it. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
