3 ms·
A lot. Semantics that can be made fast (e.g. C vs Python) with little effort. (Some languages with bad semantics for that might still get fast, but the languag
by coldtea 5y ago
A lot. Semantics that can be made fast (e.g. C vs Python) with little effort.
(Some languages with bad semantics for that might still get fast, but the language itself isn't designed to help that. JS for example was made fast, but with tons of effort but with tons of money and man-centuries thrown in by Google, Apple, Mozilla, MS, not the kind of recources available to most languages. So, I'd call a language whose semantics afford optimization a fast language).
Runtime complexity (e.g. "zero overhead" vs "lotsa overhead" features).
Also, I find the "language vs compiler" dicthotomy pedantic and tedious. For most languages and most use cases, there's a single dominant canonical version, e.g. CPython, Matz's Ruby, Oracle's Java.
Just because there are niche other implementations all 10 people use doesn't change the fact that 90% of users will be on the canonical implementation, and for them, THAT's synonymous with the language, not just some abstract spec.
- igouy 5y ago> … single dominant canonical version, e.g. CPython, Matz's Ruby… Matz's Ruby MRI? No — "Since Ruby 2.6 introduced MJIT in 2018, its performance greatly improved" https://www.ruby-lang.org/en/news/2021/11/09/ruby-3-1-0-preview1-released/ https://www.ruby-lang.org/en/news/2021/11/09/ruby-3-1-0-prev...