Saving Money by Switching from PHP to D
dlang.org
dlang.org
I'm willing to bet they didn't even try a single one of the many possibly optimizations they could have used and actually stay either in PHP or a subset of PHP. It's so much easier to win your argument with a strawman, not to say there aren't cases where D is, in fact, better.
https://stackoverflow.com/questions/1408417/can-you-compile-...
In author's case, it was rather simple I would say: they have acquired an extensive experience in D language and saw its potential by switching from PHP for good.
Could they have used swoole and go fully concurrent and asynchronous with PHP, while maintaining their legacy system? Yes.
Could it perform? With swoole, they could outperform Golang under specific use-cases and circumstances.
But that's not author's point.
Their point is, they have used a language and have saved a lot of money for their business.
Could they have done the same with PHP? I cannot say, I do not know; what I do know though is that a static typed programming language is ideal for writing performant code, especially for businesses that deal with ads, marketing, FinTech, Banking, and Medical systems to say the least.
Personally, if I switched away from PHP for web development these days I would do the backend in Go. But thank you for teaching me something new today. SCGI is not a protocol I'd heard of before, what with FastCGI being the (horribly legacy) standard. I have something new to research. :)
I love scgi because it's clean and easy to implement. And it works fine for our use cases.