4 ms·

Counterexample: the fact that there is only a single official go compiler is great advantage IMO since it enables a lot of cool tooling and great new features a

by lpapez 4y ago

Counterexample: the fact that there is only a single official go compiler is great advantage IMO since it enables a lot of cool tooling and great new features are introduced quickly in the official implementation.

edgyquant 4y ago
Doesn’t Go also have a GCC version?
- Conan_Kudo 4y ago
  It does. GCCGO is often used for bootstrapping golang, and is sometimes used as a full alternative compiler for architectures that Google refuses to consider supporting.
simplotek 4y ago
> since it enables a lot of cool tooling What leads you to believe that the lack of alternatives leads to enabling "a lot of cool tooling"? > and great new features are introduced quickly in the official implementation. That has zero to do with existing only a single implementation, and everything to do with having developers working on unstable releases and a poor job thinking things though by writing stuff down both as proposals and specifications. If there is a specification that was discussed and thought-through by competent individuals, nothing stops anyone in the world from reading the specs and implementing the same features.
- pornel 4y ago
  > What leads you to believe that the lack of alternatives leads to enabling "a lot of cool tooling"? Rust projects have settled on Cargo, which gives them uniform way of building, testing, getting dependencies, docs generation (https://docs.rs https://docs.rs), IDE support, etc. (https://lib.rs/development-tools/cargo-plugins https://lib.rs/development-tools/cargo-plugins) Contrast this with C which has several compilers and plenty of build systems to choose from, often more flexible and advanced than Cargo, but the fragmentation means that C projects are snowflakes, and tooling needs to be configured for each project and compiler combo. For every build system X there's someone who says it sucks and you should be using Y instead. However, I don't think GCC will cause similar fragmentation problems for Rust, because there are already 100K rustc+Cargo packages in existence, so it has no choice but to follow and be compatible with them.
  - surajrmal 4y ago
    Cargo is not universal. Many projects use rustc directly with an alternative build system such as bazel, make, or meson as they are in multilingual repos. The fact these projects exist doesn't affect your experience with rust. The fact a gcc tool chain for rust will exist should similarly not affect your experience.
yencabulator 4y ago
gccgo was released in 2012. https://go.dev/doc/install/gccgo https://go.dev/doc/install/gccgo https://www.gnu.org/software/gcc/releases.html https://www.gnu.org/software/gcc/releases.html

by lpapez 4y ago

edgyquant 4y ago

Doesn’t Go also have a GCC version?

Conan_Kudo 4y ago
It does. GCCGO is often used for bootstrapping golang, and is sometimes used as a full alternative compiler for architectures that Google refuses to consider supporting.

simplotek 4y ago

> since it enables a lot of cool tooling What leads you to believe that the lack of alternatives leads to enabling "a lot of cool tooling"? > and great new features are introduced quickly in the official implementation. That has zero to do with existing only a single implementation, and everything to do with having developers working on unstable releases and a poor job thinking things though by writing stuff down both as proposals and specifications. If there is a specification that was discussed and thought-through by competent individuals, nothing stops anyone in the world from reading the specs and implementing the same features.

pornel 4y ago
> What leads you to believe that the lack of alternatives leads to enabling "a lot of cool tooling"? Rust projects have settled on Cargo, which gives them uniform way of building, testing, getting dependencies, docs generation (https://docs.rs https://docs.rs), IDE support, etc. (https://lib.rs/development-tools/cargo-plugins https://lib.rs/development-tools/cargo-plugins) Contrast this with C which has several compilers and plenty of build systems to choose from, often more flexible and advanced than Cargo, but the fragmentation means that C projects are snowflakes, and tooling needs to be configured for each project and compiler combo. For every build system X there's someone who says it sucks and you should be using Y instead. However, I don't think GCC will cause similar fragmentation problems for Rust, because there are already 100K rustc+Cargo packages in existence, so it has no choice but to follow and be compatible with them.
- surajrmal 4y ago
  Cargo is not universal. Many projects use rustc directly with an alternative build system such as bazel, make, or meson as they are in multilingual repos. The fact these projects exist doesn't affect your experience with rust. The fact a gcc tool chain for rust will exist should similarly not affect your experience.

yencabulator 4y ago

gccgo was released in 2012. https://go.dev/doc/install/gccgo https://go.dev/doc/install/gccgo https://www.gnu.org/software/gcc/releases.html https://www.gnu.org/software/gcc/releases.html