rfc:php6

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
rfc:php6 [2014/07/22 14:14] – More minor changes. zeevrfc:php6 [2014/07/23 13:36] – Put to vote. Again. ajf
Line 1: Line 1:
 ====== PHP RFC: Name of Next Release of PHP ====== ====== PHP RFC: Name of Next Release of PHP ======
   * Version: 2.0   * Version: 2.0
-  * Date: 2014-07-05 (latest 2014-07-20+  * Date: 2014-07-05 (latest 2014-07-22
-  * Author: Andrea Faulds <ajf@ajf.me>, Zeev Suraski <zeev@php.net> +  * Authors: Andrea Faulds <ajf@ajf.me>, Zeev Suraski <zeev@php.net> 
-  * Status: Under Discussion+  * Status: In Voting
   * First Published at: http://wiki.php.net/rfc/php6   * First Published at: http://wiki.php.net/rfc/php6
  
Line 42: Line 42:
   * Skipping versions isn't unprecedented or uncommon in both open source projects and commercial products.  MariaDB, jumped all the way up to version 10.0 to avoid confusion, Netscape Communicator skipped version 5.0 directly into 6.0, and Symantec skipped version 13.  Each and every one of those had different reasons for the skipping, but the common denominator is that skipping versions is hardly a big deal.   * Skipping versions isn't unprecedented or uncommon in both open source projects and commercial products.  MariaDB, jumped all the way up to version 10.0 to avoid confusion, Netscape Communicator skipped version 5.0 directly into 6.0, and Symantec skipped version 13.  Each and every one of those had different reasons for the skipping, but the common denominator is that skipping versions is hardly a big deal.
   * Version 6 is generally associated with failure in the world of dynamic languages.  PHP 6 was a failure;  Perl 6 was a failure. It's actually associated with failure also outside the dynamic language world - MySQL 6 also existed but never released.  The perception of version 6 as a failure - not as a superstition but as a real world fact (similar to the association of the word 'Vista' with failure) - will reflect badly on this PHP version.   * Version 6 is generally associated with failure in the world of dynamic languages.  PHP 6 was a failure;  Perl 6 was a failure. It's actually associated with failure also outside the dynamic language world - MySQL 6 also existed but never released.  The perception of version 6 as a failure - not as a superstition but as a real world fact (similar to the association of the word 'Vista' with failure) - will reflect badly on this PHP version.
- +  * The case for 6 is mostly rebuttal of some of the points abovebut without providing a strong case for why we *shouldn'tskip version 6.  If we go with PHP 7the worst case scenario is that we needlessly skipped a version.  We'd still have an infinite supply of major versions at our disposal for future use.  If, however, we pick 6 instead of 7 - the worst case scenario is widespread confusion in our community and potential negative perception about this version.
-To summarize, version 6 is already taken by highly publicized project that is in the minds of a very large chunk of PHP developersinternals and general PHP community alike. +
-The proposal to reuse it for something completely different **will gain us absolutely nothing**, unless our goal is to needlessly confuse our users.+
  
 As a special non serious bonus, 7 is perceived as a lucky number in both the Western world and Chinese culture.  A little bit of luck never hurt anybody.  [[http://en.wikipedia.org/wiki/Numbers_in_Chinese_culture]] (no, we're not truly seeing it as a real advantage - the case for 7 is very strong without it). As a special non serious bonus, 7 is perceived as a lucky number in both the Western world and Chinese culture.  A little bit of luck never hurt anybody.  [[http://en.wikipedia.org/wiki/Numbers_in_Chinese_culture]] (no, we're not truly seeing it as a real advantage - the case for 7 is very strong without it).
 +
 +==== Summary ====
 +
 +Version 6 is already taken by a highly publicized project that is in the minds of a very large chunk of PHP developers, internals and general PHP community alike.
 +
 +We risk nothing by calling it PHP 7.  We risk confusion and negative perception if we insist on reusing 6 for a completely different project.
 +
 +Taking a risk that stands to yield absolutely no reward is not a good strategy.
 +
  
 ===== The Case for PHP 6 ===== ===== The Case for PHP 6 =====
Line 64: Line 71:
  
 Voting started 2014-07-20 but was cancelled. Voting started 2014-07-20 but was cancelled.
 +
 +Voting restarted 2014-07-23 afresh and ends 2014-07-30.
 +
 +<doodle title="Shall the name of PHP NEXT be PHP 6, or PHP 7?" auth="user" voteType="single" closed="false">
 +   * PHP 6
 +   * PHP 7
 +</doodle>
  
 ===== References ===== ===== References =====
rfc/php6.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1