5 ms·
This is for both development on ARM systems (standard go commands, eg: go build, etc) and deploying to ARM systems (setting ARM as a compile target). That said,
by ihsw 11y ago
This is for both development on ARM systems (standard go commands, eg: go build, etc) and deploying to ARM systems (setting ARM as a compile target). That said, I'm genuinely curious why anyone would develop on an ARM-based system as opposed to your run of the mill desktop.
I realize that standard towers may be supplanted by their SoC brethren, but so what? Will we all be using iMac-like computers as desktops in the next 36-72 months? Will there even be any differentiation between "regular" desktops with discrete CPUs, memory, etc and the system-on-a-chip variant?
- detaro 11y agoNot everybody compiles all binaries they deploy on developer workstations. If you run ARM servers, it makes sense that your build servers are on ARM as well, especially since you should run tests on the same architecture you're deploying to.
- ersoft 11y agoWell, when your build takes 1min on ARM and 3 seconds on your laptop, it makes sense.
- laurent123456 11y agoI run a Go program on a Raspberry Pi device, and it's actually very convenient to be able to quickly edit a Go file, and test with `go run` directly on the machine.
- GauntletWizard 11y agoI also run go on RPi, and compiled either there or on a qemu layer because the support for cgo cross-compilation for ARM was lacking. This was back in 1.3; It may be better now.
- laurent123456 11y agocgo support seems fine, at least for my use. I've compiled and use the go-sqlite3 package without any problem.
- swiley 11y agoIt's nice to be able to run go and vim on my phone when I want to.
- melling 11y agoHey, looks like someone answered you today: http://techcrunch.com/2015/11/17/google-and-asus-launch-the-85-chromebit-a-chrome-os-desktop-on-an-hdmi-stick/#.85ahlt:iqVE http://techcrunch.com/2015/11/17/google-and-asus-launch-the-...