The key is if you can write superior code.
Actually, I think it is more about the design and algorithms in the overall system
rather than the coding itself.
And design/algorithms are completely independent of the language used.
Coding is a very small part of an overall project and
IMO the actual language used is pretty irrelevant.
You can have brilliant, excellent, fast, and superior code within individual components
but put the pieces together in a poor design and the system will not work very well.
I used to have a saying, I used quite a bit in the past:
"Better algorithms, beats faster code every time".
i.e. a much better algorithm or system design written in interpreted BASIC could potentially
outperform a poor design written in assembler.
The moral is spend time up front to examine the system as a whole
and deal with things at a system level (before coding)
rather than try to optimize things down at the function/coding level.
Sometimes there are unknowns where some experimental trial/error coding is necessary
but those are often not the norm.
--- bill