2 ms·
> it does not make sense to call Rust "proprietary" because it only has a living specification, It doesn't have a "living specification", it has a reference i
by lelanthran 4y ago
> it does not make sense to call Rust "proprietary" because it only has a living specification,
It doesn't have a "living specification", it has a reference implementation. There's a difference. HTML is a living specification without a reference implementation. Rust (and many other languages) have a reference implementation without a living specification.
> The only reason people wouldn't call your changes "Rust" is because the community doesn't share the same expectations
That's not true; you cannot call it Rust because Rust, the programming language, is trademarked.
It is protected, you understand? There are legal barriers to calling your NewLanguage "Rust", as explained by the foundation themselves over here: https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/ https://foundation.rust-lang.org/policies/logo-policy-and-me...
Writing your own language and calling it Rust is legally forbidden.[1] You are, of course, free to use the permissive copyright but the name is trademarked.
Now, with C, OTOH, as an ISO standard it has no trademark so this argument does not even arise.
[1] As far as I can tell, it would be legally forbidden even if your new implementation of Rust behaves identical to the reference implementation. The best you can do is call it Rust compatible.