Security ImprovementsĪs PHP changes and improves through new PHP versions, so grow vulnerabilities. Luckily, performance improvements in PHP are almost constant between versions, with even “minor” versions like PHP 7.3 giving double digit performance improvements in popular PHP-based web content management systems. More, they often need to provide that fast and reliable experience at scale, and do it with as little overhead as possible. As we mentioned earlier, in order to stay competitive, or even relevant, applications and websites must deliver a fast and reliable experience while providing their requisite functionality. Performance ImprovementsĪ hugely important point of improvement for PHP versions lies in the advancements in PHP performance. Without a constant stream of new features, developers wouldn’t be able to leverage the big ideas and technologies in the greater development umbrella – think CI/CD, microservices, serverless, etc. And, while new features and usability improvements may not cause droves of developers to adopt a particular PHP version over another, these incremental improvements do help to keep developers using the language in the long term. While the process may seem convoluted and borderline bureaucratic, the constant improvements and features make the process emphatically worthwhile and help to keep the language true to the vision of those who work with it most.Īs we mentioned earlier, the RFC process drives many types of improvements. The PHP community within the RFC process will consider the performance impact, backwards compatibility, implementation consistency, and other factors for each new proposed feature. The RFC process also ensures that there is ample discussion and consideration for new features and their potential consequences. Some proposals may implement multiple votes, such as when there are two alternate ideas within the proposal without a clear front-runner. The vote can result in the inclusion of the fully-developed change proposal, outright rejection of the proposed change, or a recommendation to go back to the review and discussion process. There, once questions about the proposal have been addressed, and two weeks have elapsed, the proposal can be brought to a vote. Then, once the RFC is ready, the author changes the status to under discussion and sends an email to the internals list introducing the RFC. If feedback is positive (or not negative, as the how-to doc states) users are then free to create an RFC (as long as they have the requisite RFC karma). The proposal is then discussed (if not discussed, it’s essentially dead on arrival). The process starts with a warning, “If you don't have the skills to fully implement your RFC and no one volunteers to code it, there is little chance your RFC will be successful.” For those brave enough to venture forward with their proposal, the next step is to email the internal discussion list with who will implement the idea, and “whether the proposal is only a ‘concept’”. The RFC allows developers to submit suggestions for features, performance improvements, and other changes, then discuss them within the highly-involved PHP community. In PHP, new features find their way into the language via proposals submitted as "Requests for Comments" or RFCs.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |