4 ms·
I would say give it time, you can't measure Rust with this yardstick (yet), Rust is a baby in terms of age. Let's not forget that C is ~50 years old and yet ha
by elteto 6y ago
I would say give it time, you can't measure Rust with this yardstick (yet), Rust is a baby in terms of age.
Let's not forget that C is ~50 years old and yet having reliable, open-source, high-quality compilers is a thing of the past 20 years or so. Clang was born in the 2000's, GCC is much older but it wasn't that great of a compiler for some time. Same with VS.
- fiddlerwoaroof 6y agoAs far as I know, though, C has had multiple implementations for years: IBM has its own compiler, Sun had one, Borland and all sorts of other vendors had one. It seems to me that C comes from an era where languages were standardized and multiple vendors provided their own implementations: Common Lisp, Ada, Fortran, even a relatively obscure language like Eiffel all fit this criteria.
- moocowtruck 6y agoyep multiple implementations and glorious code work around for each one of them! ahh those were the days
- elteto 6y agoThis might be an overly rosy view of history :) prior to 89 C wasn’t even standardized, and C++ was a mess until 98. And those are just the years that the standards came up. It took time for existing compilers to catch up.
- fiddlerwoaroof 6y agoI’m somewhat familiar with this: I write a lot of Common Lisp and try to stick to the portable features (standard + compatibility libraries). So, I occasionally find issues with particular implementations.