PHP case study: resisting the switch to Scala, Rust, or Go - eviltoast
Case study - Upply: The PHP advantage: How we resisted the switch to Scala, rust, or go (Symfony Blog)
symfony.com
Relaunching our Symfony case studies! Discover how Upply tackled tough tech decisions like sticking with PHP for scalability and performance with Florent Laval

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

  • brie@programming.devEnglish
    1·
    3 days ago

    Because writing web apps is boring as fuck, and evaluating switching provides a reason to stop coding in PHP, and write an article about how they still need to write PHP.