C interpreter -> http://root.cern.ch/drupal/content/cint
Java compiler to native code -> http://www.excelsior-usa.com/jet.html
C interpreter -> http://root.cern.ch/drupal/content/cint
Java compiler to native code -> http://www.excelsior-usa.com/jet.html
However, reality is that most languages' ecosystems and performances are tightly connected to one or two implementations.
I find sad that young generations mix languages with implementations and get wrong concepts that a certain language can only be implemented in a specific way.
Yes, but the parent that you responded to wasn't really susceptible to this. It's quite natural to speak of the "performance properties of Language X" as if you were to say, "the performance properties of the most widely used implementation of Language X."
English doesn't lend itself well to precision. Therefore, people rely on the ability of others to use contextual clues to infer assumptions.
It's pretty clear in this case what point the parent was trying to convey.
And I'm not sure what youth has to do with any of this.
I am already old enough to have coded Z80 assembly back in the day and I see this mix of languages and implementations mostly around youth wannabe programmers.