> There's a reason it took a decade to get projects onto python 3, but PHP can swiftly move the entire ecosystem from v5 to v7 in a year. PHP did well with v5

> There's a reason it took a decade to get projects onto python 3, but PHP can swiftly move the entire ecosystem from v5 to v7 in a year. PHP did well with v5 to v7. It took more than a year but your point is well made. The PHP v7 to v8 move is not as easy [1, 2, 3]. Not having Python 2 to 3 fresh in everyone's minds is one reason; not having failed PHP v6 is another. The breakages that led to the downfall of PHP6 made backwards compatibility a focus in PHP7. Since PHP7 was released the contributors/voices who favour backwards compatibility have left or been drowned out. The emphasis on supporting legacy code has gone. [1] https://stitcher.io/blog/new-in-php-8#breaking-changes https://stitcher.io/blog/new-in-php-8#breaking-changes [2] https://24daysindecember.net/2020/12/21/a-perfect-storm/ https://24daysindecember.net/2020/12/21/a-perfect-storm/ (recommended reading) [3] https://developer.yoast.com/blog/the-2020-wordpress-and-php-8-compatibility-report/ https://developer.yoast.com/blog/the-2020-wordpress-and-php-...