This is the standard performance-tuning discussion, in a different guise.
Until you explain what factor(s) you're optimizing for, "It's faster because it's written in (whatever)" is a canard.
You can take that discussion in most any direction.
Budget. Even free coders and open-source has its costs.
Raw speed? Custom hardware? Hand-tweaked assembler? FPGA?
Speed, but without the budget for bumming instructions? Architecture- or machine-dependent C code?
Staffing? Enterprise plug-compatible Java.
Maintainability? Not everybody can hack source code in Bliss or some other obscure or domain-specific languages.
I/O? Does removing the rotating rust from the design help?
Memory footprint or ROM space, the available languages, the stinky compiler that's available on (expurgated), or whatever other factors are key to your goals...
To paraphrase that ancient Microsoft slogan, what are you optimizing for today?
Until you explain what factor(s) you're optimizing for, "It's faster because it's written in (whatever)" is a canard.
You can take that discussion in most any direction.
Budget. Even free coders and open-source has its costs.
Raw speed? Custom hardware? Hand-tweaked assembler? FPGA?
Speed, but without the budget for bumming instructions? Architecture- or machine-dependent C code?
Staffing? Enterprise plug-compatible Java.
Maintainability? Not everybody can hack source code in Bliss or some other obscure or domain-specific languages.
I/O? Does removing the rotating rust from the design help?
Memory footprint or ROM space, the available languages, the stinky compiler that's available on (expurgated), or whatever other factors are key to your goals...
To paraphrase that ancient Microsoft slogan, what are you optimizing for today?