|
|
Log in / Subscribe / Register

Rust and GCC, two different ways

Rust and GCC, two different ways

Posted Oct 11, 2021 18:52 UTC (Mon) by dpc (guest, #74012)
In reply to: Rust and GCC, two different ways by tialaramex
Parent article: Rust and GCC, two different ways

Multiple compilers (and the official spec/standard that comes along with it) is just a hindrance. It made sense in the era of paid, propriety programming languages, OSes and their vendors, etc. When the language *is* an open source, very liberally licensed, free, portable implementation, there is really no big need to have any additional implementations. What we need is more features: more supported platforms, etc. It might be achieved by a different compiler implementation (framework) or reusing parts of it, sure And there are some big benefits of multiple compiler implementation, like trusted bootstrapping. But in itself it's a cost, not a feature.


to post comments

Rust and GCC, two different ways

Posted Oct 18, 2021 4:17 UTC (Mon) by flussence (guest, #85566) [Link] (1 responses)

> When the language *is* an open source, very liberally licensed, free, portable implementation, there is really no big need to have any additional implementations.

Anyone who tried to use such an open spec on Microsoft platforms that claimed to support it between at least 2000-2010 would probably disagree with that point. C, HTML, Java, POSIX...

Rust and GCC, two different ways

Posted Oct 18, 2021 8:35 UTC (Mon) by farnz (subscriber, #17727) [Link]

Those are additional implementations of the standard that weren't liberally licenced, free or portable. Which kinda emphasises dpc's point - multiple specification-compliant implementations is only beneficial if all implementations are of high quality.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds