Why switch if you don't need to?
this post was submitted on 18 Dec 2024
12 points (83.3% liked)
PHP
560 readers
1 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
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).
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.
Personally I doubt I'll ever reach the switching point. But the trend for PHP devs seems to be switching to Go (when they do switch).
Go is really nice! Though I prefer using both instead of a single one. Still hoping to come across a problem which could be solved by running a Go library using FFI in PHP.