179 - PHP has 3 problems

Changelog Code Quiz - We now have a Next JS website. This is also running a Docker image. No React components yet. - Docker compose files are now in the root directory Contributions welcome: https://github.com/howToCodeWell/code-quiz Ideas for the future Store Quizzes in Markdown files instead of PHP fixtures Simplified - We have a single source of truth for code questions Future proofing - We can use code snippets in the questions PHP has these three problems PHP has too many BC breaks which is making library authors uncomfortable Voting is too centralised. You have to be in 'the club' to vote on RFCs Funding is an issue I personally think that PHP should only introduce BC breaks if: There is a really good benefit in doing so. All BC breaks should have been mentioned in the RFC with examples. BC breaks are only allowed in major releases. There is a large deprecation window between major releases. Backward compatibility is important and should prioritised over new changes. Voting is too centralised. Mailing lists suck. There are better ways to manage communication in 2022 It does feel like an elitist club. Follow the RFC guide here https://wiki.php.net/rfc/howto Funding is a problem Companies need to take PHP more seriously and pay for the communities time Companies need understand that open source comes at a cost to both them and the community Who pays for PHP https://thephp.cc/articles/who-pays-for-php Google stadia is dead https://www.protocol.com/newsletters/entertainment/google-stadia-shutdown-developers-aftermath Follow on the socials Twitter: https://twitter.com/howtocodewell Instagram : https://www.instagram.com/howtocodewell/ My web development courses ➡️ Learn How to build a JavaScript Tip Calculator ➡️ Learn JavaScript arrays ➡️ Learn PHP arrays ➡️ Learn Python ✉️ Get my weekly newsletter ⏰ My current live coding schedule (Times are BST) Tuesdays 18:00 = Live Podcast YouTube Sundays 15:00 - Live coding on Twitch