Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78317 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61596 invoked from network); 24 Oct 2014 19:59:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Oct 2014 19:59:16 -0000 Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.171 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.214.171 mail-ob0-f171.google.com Received: from [209.85.214.171] ([209.85.214.171:39121] helo=mail-ob0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 71/22-50727-39FAA445 for ; Fri, 24 Oct 2014 15:59:16 -0400 Received: by mail-ob0-f171.google.com with SMTP id wp18so897308obc.16 for ; Fri, 24 Oct 2014 12:59:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=4clCqo3atXVGWnuTMSqf5dY19oaBKZCHXQB54V/JJ5Q=; b=nT2had0kEoLn31d24o5lnEE1AxiirzJE0x8zRxd0R9XB+DBD+I7eURfY9Nl/7t7tsj YSGf09wZG6mfwRC5wgQtiCJ/dGFQ1RuV5/JwCPQo/rhAF7VTB0UlxL92xL5I2aFX7us9 5lSSTz5unN0WpTJ56VCDrPTDC+Ul/cBJXbIJmvAxE74KVG0BzfH9wTKvhELC12iGwDHh jFCBi6tN8fw4VeBzcyUZZAZKhsJOoH3CN6ymPDFjvmU1Gj04ly8YMScqyHsDxAXWBBqn pGqV8ojAU0lZ5to51Fr9wzzQVw1jkYtmGt9oHhGV0Fw98bc5CAukRGE4223sCRx/fVVg Gchw== MIME-Version: 1.0 X-Received: by 10.202.200.5 with SMTP id y5mr1901039oif.97.1414180753263; Fri, 24 Oct 2014 12:59:13 -0700 (PDT) Sender: morrison.levi@gmail.com Received: by 10.76.75.37 with HTTP; Fri, 24 Oct 2014 12:59:13 -0700 (PDT) In-Reply-To: References: Date: Fri, 24 Oct 2014 13:59:13 -0600 X-Google-Sender-Auth: YD9Lom2SuyvOsHnbVBzRN9vLV44 Message-ID: To: Andrea Faulds Cc: Daniel Ribeiro , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Thoughts on the PHP.net website From: levim@php.net (Levi Morrison) >> 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 day= s >> for building websites? > > Interesting? Maybe. A good idea? Definitely not. > > If there=E2=80=99s one rule in refactoring, it=E2=80=99s that you never d= o ground-up rewrites of something which works. They always go badly. If the= re 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.