I mean. There's plenty of languages that have this overhead.

A base Laravel or symfony installation shows a landing page in 30-50ms (probably).

I've written ( in a lightweight framework rather that no longer exists ) a program to encrypt/decrypt strings using XML messages over http requests.

The whole call took 40-60ms. About 40-50% of that was the serializer that needed to be loaded. The thing was processing a few hundred request per minute in peak. Which is a lot more than the average nextcloud installation. The server wasn't really budging ( and wasn't exactly a beast either ).

I'm definitely not refuting that the JIT compiler adds overhead. But as in my example above, it's also not like it's adding 100ms or more per request.

If you have a very high performance app to the point where you're thinking about different transport than HTTP because of throughput you're likely better off using something else.

Circling back to the original argument my feeling remains that the same codebase in GO or RUST wouldn't necessarily perform a lot better if you just calculate in php speed and the overhead of the JIT compiler.

If you'd optimize it in rust/go. It likely will be faster. But I feel like the codebase could use some love/refactoring. But doing that is more difficult when you already have:

• a large user base on various hardware
• a large Plugin community which will need to refactor all their plugins
• need some compatibility with all the stuff that is already there ( files, databases, migrations)

You don't want to piss off your entire userbase. Now I feel like I'd like to try it myself and look at the source though :'). ( I'm not saying I can do better though. It's been a couple of years).