It sounds like the exec made the right choice. PHP is a wildly successful language that powers an obscene portion of the Internet web apps.
That’s not a “bad” language, it’s just an annoying one for engineers to work with. A bad language would be one with so little adoption and such a steep learning curve that hiring new software engineers is a year-long path to expanded productivity.
I actually covered this in literally the next line.
> 1) Programming language quality is a non-factor in business success.
What TeMPOral wrote (below) is is not quite the same in my view. First, they elaborate more. Second, there is a different argument:
> Software side has so much slack in it that it can (and often does) do extremely bad job at making the actual thing and still succeed.
Namely: it is NOT the case that software does not have a business effect. Rather, other aspects of the business have to work extra hard to compensate.
To take a systems point of view: two systems can have the same output over some time period but very different internal efficiencies.
That assumes that the software business is efficient in the market sense, which my experience suggests is very much not true. On the contrary, I've found that success hinges primarily on the ability to find and execute good business deals (which is the work of executive team and/or sales&marketing). Software side has so much slack in it that it can (and often does) do extremely bad job at making the actual thing and still succeed.
> I have never seen a non-programmer executive demand a “bad” language be used for a startup.
I've worked for one many years ago. I was actually promised the free reign over technology stack for a project, until the CEO decided to override me and order me to use a very particular and shitty combination of technologies. He was very up-front with me about his reasoning: he said, "yeah, I could let you write this in something more reasonable, say Ruby or Python, but programmers for those languages are expensive, PHP programmers are much cheaper, and I'm going to be hiring more people to help you".
(I run the project solo for the next year, because he eventually decided not to hire anyone.)
> picking the boring language that lets the business focus on its core domain is better than picking something that excites the most vocal engineers.
Be careful not to mix up topics here. What usually "excites the most vocal engineers" these days is the things they can use to pad their CVs. This usually goes against what the management wants, which is whatever stack they've read about on HBR or whatever one is cheapest to hire people for. Neither of those tend to have anything to do with powerful and advanced tooling.