Re:Go team adding a Go language server to core
by nemothekid on Friday September 21, 2018 @08:38PM
(#18043785)
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.
Re:Go team adding a Go language server to core
by gameswithgo on Friday September 21, 2018 @07:54PM
(#18043564)
Rust has a lot of great tooling. Cargo is top notch.
The RLS implementation is not good yet though, and there is no good news in the near term for it.
Re:Go team adding a Go language server to core
by nicoburns on Saturday September 22, 2018 @07:59AM
(#18045655)
There's a thread on rust internals where planning is taking place for a long-term strategy for RLS. It looks like end of 2019 might be a realistic time frame for a compiler-backed RLS. The good news is that it looks like this work might have some significant benefits for incremental compile times too :)
Re:Go team adding a Go language server to core
by Boulth on Saturday September 22, 2018 @04:23AM
(#18045083)
> Cargo is top notch.
I agree Cargo is good but there are some issues that bug me (e.g. no support for docker layers with cargo --dependencies-only, xargo is not merged in, is there a support for custom repositories yet?).
Edit: I sound more negative than I meant. I am excited about this. It was cool that Sourcegraph and the VS Code extension pioneered here, but it's exciting to have official support and a place for everyone to rally for improvements. I look forward to seeing this used in things like Theia, VS Code, etc.