Internals link: https://externals.io/message/127120

Note: I am not the RFC author.

• Internals discussion: https://externals.io/message/127047
• Prior similar RFC: https://wiki.php.net/rfc/array_key_first_last

Note: I am not the RFC author.

I noticed that if you have too few pm_children set then some requests hang until timeout. This surprised me - I'd expect an immediate error, but it's more like a tarpit! For ages I was thinking my server was not performant, then I noticed via top that it wasn't doing or waiting while the browser was.

I have two questions:

1. If you have pm_max_children=1 and you occupy that and submit another request, what actually happens? (I'm proxying through nginx.) HTTP doesn't have a "40_ Come back later".
2. (if life deals you lemons...) if you can generate a tarpit that doesn't use server resources, this could be quite useful to know about too!

A summary of the highlights and key accomplishments of the Symfony project in 2024.

My TLDR is:

• Their team was using PHP
• Before doing a complete re-write they evaluated other languages
• Rust ruled out due to cost/benefit, being the fastest in the list, but also the most complex
• PHP kept as the main language because:
  • The ecosystem is mature
  • The PHP/Symfony (and Roadrunner) stack meets their high-performance needs
• Inertia: their team "already had extensive experience" in it
• They already integrated Go in some microservices
• They aren't locked to PHP, and will continue to evaluate these programming languages and others