![]() There are big performance-enhancing features like Just-in-Time (JIT) PHP compilation at runtime for faster execution with less memory usage. It’s far more of a balancing act than a race toward the bleeding edge. With about half the web running on WordPress, it’s a big ship that can’t turn quickly. This is a fast release cycle, and it’s no surprise the WordPress ecosystem struggles to keep up with it. PHP 8.2, which just had its first stable release, will have security support until December 2025. The current and actively supported version, PHP 8.1, will age out at the end of 2024. PHP 8.0 has less than a year left for its official security support through most of 2023. Unfortunately, PHP 7.4 just reached its EOL date at the end of November 2022. ( Statistics) PHP 7.4 Has Reached Its End-of-Life 20% are using PHP 7.0 to 7.3, and the largest group (56.7%) is using PHP 7.4. The WordPress project notes this and warns that using unsupported PHP versions “may expose your site to security vulnerabilities.” ( Requirements)įortunately, only 5.1% of all WordPress sites currently use PHP 5.6, and only 2% use an even older version. It “also works with” PHP 5.6.20, which reached its end-of-life date at the end of 2018. In contrast with WooCommerce, which requires a minimum of PHP 7.4, WordPress core currently only recommends PHP 7.4 or higher. Because backward compatibility is so prioritized, it falls to WordPress businesses to determine their own product or service life cycle. WordPress core maintains significant backward compatibility with no planned end-of-life dates when old versions won’t be supported. Keeping Up With PHP Development in WordPress How do WordPress developers maintain backward compatibility while taking advantage of new features that will benefit end users? This is a key theme in the relationship between both open-source projects. Let’s take a look at the recent evolution of PHP - and WordPress. While potentially painful - especially for WordPress core - deprecation is a key feature and a gift to developers from PHP. One of the biggest changes likely to challenge WordPress developers is the addition of readonly classes, which disallow dynamic properties.ĭynamic properties are deprecated and will produce a fatal error in PHP 9 or possibly PHP 10. ![]() PHP 8.2 introduces greater type safety as a feature with null, false, and true as standalone types. As a major update, it brings performance improvements and simpler syntax. PHP 8.2.0 made its debut on December 8, 2022. 7.2 “All programming is maintenance programming”.7.1 “Who’s going to pick up the garbage on Monday morning?”.6.1 Code That’s More Correct is Likely to Be More Secure.5.2 How WordPress Core Keeps Up with PHP and Maintains Backward Compatibility.5.1 The Beauty of Ever-Evolving, Elegant Code.Doing Without Dynamic Properties After PHP 8.2 4.1 The Glass Half Full: Deprecated Features Push PHP Developers Forward. ![]() Deprecation Notices Drive Development Forward The Best Time to Raise Your Minimum PHP Requirement
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |