jmoiron plays the blues
created gowiki, single-file single-executable wiki written in golang
created gowiki, single-file single-executable wiki written in golang
created gowiki, single-file single-executable wiki written in golang
created gowiki, single-file single-executable wiki written in golang
created gowiki, single-file single-executable wiki written in golang
created gowiki, single-file single-executable wiki written in golang
created gowiki, single-file single-executable wiki written in golang
Wrote a wiki in #golang as an experiment, single go file, all resources served from single binary github.com/jmoiron/gowiki
I wrote a little #golang database/sql FAQ/sqlx propaganda piece, which should nonetheless be informational: jmoiron.net/blog/gos-datab…
Not really the conference type, but early bird ticket for @GopherCon acquired. Never been to Denver, anyway.
Excellent talk about hardware (CPU, cache, memory) myths and realities from @mjpt777 youtube.com/watch?v=MC1EKL…
@jackzerby for sure, but "Our product is great for <intended audience>!" or "great at <details>" can be specific without pushing people away
@jackzerby "alienate people by saying your product is not for them"? just be honest with your marketing and let them decide!
@jordanorelli certainly as of april 17th 2013 it was :)
@jordanorelli LTU is full of this kind of stuff too (type system hubris). Then I remember http://t.co/je059Hfelx and laugh.
"If you find yourself writing callbacks in Go, you’re almost certainly doing it wrong.vividcortex.com/blog/2013/06/0…VD fro@xaprbrb