pplusplus:faq

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
pplusplus:faq [2019/08/12 13:24]
zeev Address some of the concerns
pplusplus:faq [2019/08/14 13:47] (current)
zeev
Line 6: Line 6:
  
 This is a clarifying FAQ for the idea presented on [[https://marc.info/?l=php-internals&m=156529545007909&w=2|internals@]].  It attempts to address many points that were raised repeatedly in the discussion that ensued. This is a clarifying FAQ for the idea presented on [[https://marc.info/?l=php-internals&m=156529545007909&w=2|internals@]].  It attempts to address many points that were raised repeatedly in the discussion that ensued.
 +
 +A [[pplusplus:concerns|list of concerns]] about this idea has been compiled by Arnold Daniels.  Some of them are addressed [[pplusplus:faq#what_are_the_general_concerns|here]].
  
 Note:  P++ is a temporary code name and is subject to change. Note:  P++ is a temporary code name and is subject to change.
Line 46: Line 48:
 ==== Why not just make a perpetual PHP 7.4 LTS and be done with it, as we move to a stricter PHP 8/9?  ==== ==== Why not just make a perpetual PHP 7.4 LTS and be done with it, as we move to a stricter PHP 8/9?  ====
  
-There are many issues with this approach Even if we disregard the fact that this leaves the huge dynamic-preferring crowd hanging with no feature or performance updates - it's impractical from a development effort point of view.  Unlike this proposal - this does, in factmean de-facto fork.+There are many issues with this approach, but these are probably the most important ones: 
 +  - For the dynamic crowd - more strictness is not equivalent to progress, and as such - they don't want to see future versions of PHP forcing them in that direction.  They still want to get other types of new features (non-strictness related), better performance, bug fixes, new extensions and such.  Making PHP stricter with newer versions means that for many users - upgrading would mean going backwards as far as their development preferences are concerned. 
 +  - Equally important - it'remarkably difficult - arguably impractical from a development effort point of view.  Unlike this proposal - which aims to continue supporting both dialects in the same codebase - having a version that would no longer be actively developedbut would still have to be maintained for security and critical bugfixes over the course of over decade requires resources that we simply don't have (it is arguably a kind of a fork).
  
 ==== Will I need to choose between PHP and P++? ==== ==== Will I need to choose between PHP and P++? ====
  
-Yes and no.  As mentioned above, when you install one - you'd have the other - so as far as apps go - you'd be able to run both dialects on a single server.  However, practically speaking, projects and individuals are likely to typically pick and standardize on one or the other - similarly to how things went down with strict_types.+Yes and no.  As mentioned above, when you install one - you'also have the other - so as far as apps go - you'd be able to run both dialects on a single server, even within the same app.  However, practically speaking, projects and individuals are likely to typically pick and standardize on one or the other - similarly to how things went down with strict_types.
  
  
Line 132: Line 136:
 Arnold Daniels compiled [[https://wiki.php.net/pplusplus/concerns|a list of concerns]] about this proposal. Arnold Daniels compiled [[https://wiki.php.net/pplusplus/concerns|a list of concerns]] about this proposal.
  
-Some of them are answered here:+Some of them are addressed here:
  
 === Converting PHP code to P++ code is not trivial === === Converting PHP code to P++ code is not trivial ===
pplusplus/faq.1565616291.txt.gz · Last modified: 2019/08/12 13:24 by zeev