Artwork

Контент предоставлен Peter Fisher. Весь контент подкастов, включая эпизоды, графику и описания подкастов, загружается и предоставляется непосредственно компанией Peter Fisher или ее партнером по платформе подкастов. Если вы считаете, что кто-то использует вашу работу, защищенную авторским правом, без вашего разрешения, вы можете выполнить процедуру, описанную здесь https://ru.player.fm/legal.
Player FM - приложение для подкастов
Работайте офлайн с приложением Player FM !

179 - PHP has 3 problems

30:01
 
Поделиться
 

Manage episode 344767998 series 2674787
Контент предоставлен Peter Fisher. Весь контент подкастов, включая эпизоды, графику и описания подкастов, загружается и предоставляется непосредственно компанией Peter Fisher или ее партнером по платформе подкастов. Если вы считаете, что кто-то использует вашу работу, защищенную авторским правом, без вашего разрешения, вы можете выполнить процедуру, описанную здесь https://ru.player.fm/legal.

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

  1. Simplified - We have a single source of truth for code questions
  2. 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:

  1. There is a really good benefit in doing so.
  2. All BC breaks should have been mentioned in the RFC with examples.
  3. BC breaks are only allowed in major releases.
  4. There is a large deprecation window between major releases.
  5. 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

  continue reading

201 эпизодов

Artwork

179 - PHP has 3 problems

How To Code Well

122 subscribers

published

iconПоделиться
 
Manage episode 344767998 series 2674787
Контент предоставлен Peter Fisher. Весь контент подкастов, включая эпизоды, графику и описания подкастов, загружается и предоставляется непосредственно компанией Peter Fisher или ее партнером по платформе подкастов. Если вы считаете, что кто-то использует вашу работу, защищенную авторским правом, без вашего разрешения, вы можете выполнить процедуру, описанную здесь https://ru.player.fm/legal.

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

  1. Simplified - We have a single source of truth for code questions
  2. 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:

  1. There is a really good benefit in doing so.
  2. All BC breaks should have been mentioned in the RFC with examples.
  3. BC breaks are only allowed in major releases.
  4. There is a large deprecation window between major releases.
  5. 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

  continue reading

201 эпизодов

Tüm bölümler

×
 
Loading …

Добро пожаловать в Player FM!

Player FM сканирует Интернет в поисках высококачественных подкастов, чтобы вы могли наслаждаться ими прямо сейчас. Это лучшее приложение для подкастов, которое работает на Android, iPhone и веб-странице. Зарегистрируйтесь, чтобы синхронизировать подписки на разных устройствах.

 

Краткое руководство