61–70 of 267 posts
Earlier quoted context omitted.
Right but if I write a program that converts code into assembly and does the optimizations automatically then I can get something better or equal to a compiler.
Isn't that exactly a compiler?
Earlier quoted context omitted.
it is absolutely a flaw in the methodology, but one I think is unavoidable without enormous resources.
I agree. I just wanted to point it out in case people took the analysis as entirely accurate without looking a little closer. I suspect the entries towards the top of the list are fairly accurate, by nature of their competitive standing in the benchmark games and their focus as languages on performance. It's much easier for an implementation difference to hide in the natural drift you see in the languages with VMs an…
So as a regular writer of TypeScript I had the exact same question as you.
Earlier quoted context omitted.
I don't use Typescript, and use Javascript only for what I have to. I don't care about the ranking of either of them, I'm just pointing out a possible flaw in the methodology that should be taken into account when looking at the numbers presented, and what I suspect is a concrete example of that. This also isn't a criticism of the benchmark game, it's well known that not every implementation is equivalent in the time…
it is absolutely a flaw in the methodology, but one I think is unavoidable without enormous resources.
https://spectrum.ieee.org/computing/hardware/the-future-of-c...
For instance, switching to ASICs or even FPGAs that are optimized to handle certain types of computations.
Just look at datacenters or mobile devices. Sure, optimizations are made to runtime environments to improve performance, and increase battery life. But you are going to see bigger gains through chip architecture. And that is what vendors focus on.
No COBOL?