PHP

560 readers

5 users here now

Welcome to /c/php! This is a community for PHP developers and enthusiasts to share and discuss anything related to PHP. From the latest updates and tutorials, to your burning questions and amazing personal projects, we welcome all contributions.

Let's foster an environment of respect, learning, and mutual growth. Whether you're an experienced PHP developer, a beginner, or just interested in learning more about PHP, we're glad to have you here!

Let's code, learn, and grow together!

founded 2 years ago

MODERATORS

[email protected]

PHP case study: resisting the switch to Scala, Rust, or Go (symfony.com)

submitted 5 days ago* (last edited 4 days ago) by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 3 days ago

The point is evaluating your stack once in a while. Eventually, you may need to switch or it may be worthwhile, even if you can stick with your current stack at a disadvantage.

For an extreme example, WordPress with crap page builders. It may not have been "that bad" when you started with it. But by now its very much worthwhile to switch. You don't "need to", but you should.

Back to this post, maybe they really are at that point that slowly switching is worthwhile. At least partially, where it makes the most sense (they mention using some microservices written in Go).