4 ms·

I've been using Go for a few months on a few different projects. Neither are my "day job". The first project is a Google Music player app for Chumby devices (

I've been using Go for a few months on a few different projects. Neither are my "day job". The first project is a Google Music player app for Chumby devices (and other similar ARMv5/v6 class devices... will probably port to Raspberry Pi if/when I ever get one). The project is pure Go at this point with its own UI toolkit based on an mmaped /dev/fb. The second project is a web service API for mobile apps plus an associated webserver. I hope more companies adopt Go, making it a viable language for commercial programming. Using it is the most fun I've had coding in years.

drivebyacct2 14y ago
If you aren't already, there are probably many people that would enjoy taking a look at that ui toolkit.
nemik 14y ago
Oh, so is the ARM support decent now? Last I read (probably too long ago) it wasn't very good. I'm still using Lua in embedded projects. It's nice, nixio libs make is very nice and integrates with C ever so easily when needed.
- luriel 14y ago
  The ARM port has improved greatly from how it was before Go1 (and even more so from where it was when Go was first announced). x64 is still the best supported arch, but everything should work on ARM fine (and quite a few optimizations have gone into that port recently, but you will need to build from the tip for that).
depsypher 14y ago
I'm hoping to use Go on a Raspberry Pi (and am currently waiting patiently for it to arrive)... but this bug worries me: http://code.google.com/p/go/issues/detail?id=909 http://code.google.com/p/go/issues/detail?id=909 Anyone know if it's a dealbreaker? I'm planning on running a webserver on it, so I imagine a GC bug would likely manifest after running long enough.
- tuxychandru 14y ago
  The bug affects application dealing with large integers which can be seen as a valid pointer within the program's address space. So, this will affect your app if it deals with large ints. There is also work underway to make the GC more precise which will avoid this problem in future.

drivebyacct2 14y ago

If you aren't already, there are probably many people that would enjoy taking a look at that ui toolkit.

nemik 14y ago

Oh, so is the ARM support decent now? Last I read (probably too long ago) it wasn't very good. I'm still using Lua in embedded projects. It's nice, nixio libs make is very nice and integrates with C ever so easily when needed.

luriel 14y ago
The ARM port has improved greatly from how it was before Go1 (and even more so from where it was when Go was first announced). x64 is still the best supported arch, but everything should work on ARM fine (and quite a few optimizations have gone into that port recently, but you will need to build from the tip for that).

depsypher 14y ago

I'm hoping to use Go on a Raspberry Pi (and am currently waiting patiently for it to arrive)... but this bug worries me: http://code.google.com/p/go/issues/detail?id=909 http://code.google.com/p/go/issues/detail?id=909 Anyone know if it's a dealbreaker? I'm planning on running a webserver on it, so I imagine a GC bug would likely manifest after running long enough.

tuxychandru 14y ago
The bug affects application dealing with large integers which can be seen as a valid pointer within the program's address space. So, this will affect your app if it deals with large ints. There is also work underway to make the GC more precise which will avoid this problem in future.