Changes between Initial Version and Version 1 of Ticket #33381, comment 92
- Timestamp:
- 03/01/2017 11:34:32 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #33381, comment 92
initial v1 1 The most conservative approach to this - raising PHP versioning while keeping the same coding standards and banning PHP godsends like namespaces and anonymous functions for the indefinite future, would allow for security backports without maintaining two versions, would do a great job testing the water, and would allow new plugins to finally begin coding with efficient constructs that WordPress documentation endorses (forget where but there are various coding examples with actions and anonymous function pairings... A beautiful thing). It would do a fair bit to encourage better plugins in the repository and would allow a user to do so just be specifying a minimum WordPress version.1 The most conservative approach to this appears to be a no-brainer - raising PHP versioning while keeping the same coding standards for core and banning PHP godsends like namespaces and anonymous functions for the indefinite future, would allow for security backports without maintaining two versions, would do a great job testing the water, and would encourage new plugins to finally begin coding with efficient constructs that WordPress documentation endorses (forget where but there are various coding examples with actions and anonymous function pairings... A beautiful thing). 2 2 3 No change to code. No duplication for security backports. Tests the water. Applies pressure to hosts without harming user experience. Please, please do this. 3 It would do a fair bit to encourage better plugins in the repository and would allow a user to do so just by specifying a minimum WordPress version. 4 5 No change to core code = no duplication for security backports. Tests the water. Applies pressure to hosts without harming user experience. Please, please do this.