4 ms·
export 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
by ShorsHammer 7y ago
export 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.
- literallycancer 7y agoAs opposed to piping curl to sh?