5 ms·
I have not experienced problems installing or updating go in 5 years of use. What problems have you experienced?
by ruffrey 7y ago
I have not experienced problems installing or updating go in 5 years of use. What problems have you experienced?
- ShorsHammer 7y agoNor have I had problems, simply saying it is too much hassle for little gain so I rarely bother, whereas with other languages it is a breeze so I update all the time. Please document your workflow to update and compare it to other modern langs, it's all relative.
- AlexCoventry 7y agoThis workflow works fine for me: https://github.com/golang/go/wiki/Ubuntu https://github.com/golang/go/wiki/Ubuntu
- ShorsHammer 7y agoOk so for ubuntu (which has what desktop share again?) > _Add a 3rd party repository to apt_ > sudo add-apt-repository ppa:longsleep/golang-backports > sudo apt-get update > sudo apt-get install golang-go > Note that golang-go installs latest Go as default Go. If you do not want that, install golang-1.13 instead and use the binaries from /usr/lib/go-1.13/bin. > If that's too new for you, try: > $ sudo add-apt-repository ppa:gophers/archive > $ sudo apt-get update > $ sudo apt-get install golang-1.11-go Am I being trolled here? How would you compare this for both memorability and user experience compared to say "rustup update"? Please take a step back and look at that question without personal bias. Please!
- pushpop 7y agoThat’s not really a fair comparison. This code is installing Go where as you’re assuming Rust is already installed in your example. Plus I’ve had way more issues with Rust versions than I have with Go. Ultimately though this all just a very small part of writing code in either language.
- herbstein 7y agoYou're right, it's assuming Rust is installed since it's talking about updating the compiler. But let's install Rust instead then: `curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs https://sh.rustup.rs | sh` Now you can `rustup install <version>` easily with everything taken care of. Of course, the latest stable release is automatically installed already. And Rust provides automatic install scripts for Windows, Mac, and Linux. Whereas Go is more involved than is expected for any modern language.
- pushpop 7y agoYou can just download the go tarball and go from there. Technically you don’t need to install Go, you don’t need environmental variables set etc. But I do get your point. You are absolutely right that go doesn’t hand hold you through that process and thus a thousand different people have a thousand different methods for doing it.
- rob74 7y agoWell, using apt is one of the standard ways of installing/updating software on Linux, so most advanced Linux users should be familiar with that. But I'm sure you can also use a graphical package manager to do the same thing. "Rustup" on the other hand is a customized rust-specific tool, so of course it's easier to use (once Rust is installed)
- jorams 7y agoThis comparison is entirely unfair, because you're not comparing the same thing. This is what one has to do to install Rust: # Install rustup curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh # It automatically installs the latest version This is what one has to do to install Go: # Add the PPA sudo add-apt-repository ppa:longsleep/golang-backports # Fetch information from the PPA sudo apt-get update # Install Go sudo apt-get install golang-go 1 command vs 3, but in both cases only one "odd one" you have to remember specifically. More important, however, is the fact that from now on Go will update along with the rest of you system. You upgrade your system like this: # Upgrade the system apt-get update && apt-get upgrade rustup turns that into the following: # Upgrade everything apt-get update && apt-get upgrade # Upgrade Rust rustup update Now I'm not trying to say rustup is necessarily worse than Go, because it does offer advantages, but for the simple use-case of always running stable it adds an extra step rather often, instead of once.
- 1337shadow 7y agoJust upload your 3 lines in a gist and curl pipe bash it if that's the issue ...
- ShorsHammer 7y agoThat is good advice. I really should document it but only use go now and then for various reasons and never seem to enjoy updating, don't really have a horse in this race. It just feels so clunky, which was my original point.
- ShorsHammer 7y ago>This comparison is entirely unfair Updating rust: "rustup update" Updating Go: Search a bunch of stuff and then do the stuff some random website tells you. Entirely stand by my earlier statements. Apparently the thousands of paid computer scientists at google are simply incapable of automating the basic process to update their lang. It's utterly absurd and should be actively mocked by anyone with half a clue. We should mock this stuff, we really should, it's hilariously dumb. How are all the people getting paid SF wages literally incapable of creating "go update"?
- dnautics 7y agothis workflow works for me: https://sylabs.io/guides/3.4/user-guide/quick_start.html#install-go https://sylabs.io/guides/3.4/user-guide/quick_start.html#ins...
- ShorsHammer 7y agoexport VERSION=1.12 OS=linux ARCH=amd64 && \ # Replace the values as needed wget https://dl.google.com/go/go$VERSION.$OS-$ARCH.tar.gz && \ # Downloads the required Go package sudo tar -C /usr/local -xzvf go$VERSION.$OS-$ARCH.tar.gz && \ # Extracts the archive rm go$VERSION.$OS-$ARCH.tar.gz # Deletes the ``tar`` file # Set the Environment variable PATH to point to Go echo 'export PATH=/usr/local/go/bin:$PATH' >> ~/.bashrc && \ source ~/.bashrc Please tell me you are kidding. This is literally what you posted on how to update go. How would you compare this to say "rustup update"? How would one do this this same workflow you posted on other platforms? How memorable is it would you say? Can you do it freehand without looking it up? Is this considered good UX for developers? Looking forward to your answers here, thanks.
- code_sloth 7y agoAll the instructions basically boil down to: 1. download version X of go 2. Unpack to location Y 3. Tell your OS to look at Y Sure it's not a single command, but it's hardly complicated. If by UX you mean some kind of install script that handles those things you can always write it yourself.
- ShorsHammer 7y ago> those things you can always write it yourself The idea of everyone repeating themselves over and over again seems to be almost desirable amongst the community. The concept of DRY is essentially dead as far Go is concerned. Why exactly can the core team not write this tooling? Why should thousands of independent people do it all themselves to varying degrees? It's a laughable situation.
- dnautics 7y agoapologies, I was being snarky. Around when I was told to run this command was when I stopped using go.
- deleted 7y ago[deleted]