3 ms·
You should at least wait until there is more than one working/usable compiler for the language if you're going to start making systemic changes to your multi-bi
by modshatereality 4y ago
You should at least wait until there is more than one working/usable compiler for the language if you're going to start making systemic changes to your multi-billion-dollar code base responsible for the commerce of multiple billions of people on the planet. It's a weird move at this point for google to be making(edit: considering go is already supported on multiple compilers).
- insanitybit 4y ago"It should have two compilers" is a pretty arbitrary benchmark for production readiness. I'd suggest the benchmark be based on, idk, something with any fucking meaning.
- modshatereality 4y ago>something with any fucking meaning So you claim to have a better metric, feel free to share it? site broken and wont let me reply any more: "shipped into production" is meaningless, compilers are directly related to language community and complexity.
- insanitybit 4y agoHow about numerous companies shipping Rust to production for years? That metric is actually related to risk with regards to shipping rust in production, unlike number of compilers, which signifies nothing.
- dagmx 4y agoMany languages had only a single compiler implementation when they were brought into the limelight for critical development so your benchmark would fail almost everything.