3 ms·
The reason Go took so long with modules is another function of large corporations. Google doesn’t use modules internally (they have the monorepo) so having a mo
by nemothekid 8y ago
The reason Go took so long with modules is another function of large corporations. Google doesn’t use modules internally (they have the monorepo) so having a module system wasn’t important.
Rust may have been further along on this path, but in the grand scheme of things Go 1.1 feels far more “complete” than Rust 2015 - and a large part of that is Go’s huge standard library that Google could fund to develop.