BTW, my demo site is running in my bedroom on a slow ARM5-based debian box over my terribly slow DSL. If things get slow, that's why.
The web server itself is a homemade http server I wrote in go and jokingly called "nging". Doing a lot of SSI and transfer compression can be a bit much for that machine, but it got easier than maintaining my nginx config on upgrades.
I happened to have DB logs up and some some queries that weren't me and traced it back here. Good morning, HN.
If I may ask, why Go? As an excuse to exercise your Go skills, or did you pick it for some specific reason? (In other words, were you doing this for Go, or doing Go for this?)
All I saw on the entry was a blurb about its concurrency features.
What else would I use? I've been writing tons of go code for nearly three years now. I get fast, concurrent, parallel code in very little time.
I was pretty much production-ready with seriesly in two weeks by myself (though I'm starting to get contributions from other users). Last night, I closed my last open issue "bulk interface" by making an optional memcached binary protocol interface with custom packets for database selection and streaming data in.
Today, I started a new project with a new guy, and got some pretty impressive internal demos working after a couple hours of work.
I get lots of things done fast and reliably. This doesn't happen as much for me in other languages. I went into more details in the follow-up post where I described how I built seriesly (and keep in mind, I wrote this after it had only been alive for two weeks): http://dustin.github.com/2012/09/13/inside-seriesly.html
Sorry, I didn't know your history. I was truly curious to know if this was a problem you decided to solve strictly so you could use Go, or if that was just your, pardon me, "go to" language. It appears the latter. I hope I'm not implying that you SHOULDN'T have used it; my query was truly just curiosity, since I'm curious about the language. I'm trying to get a feel for what other people are doing with it "for real".
The web server itself is a homemade http server I wrote in go and jokingly called "nging". Doing a lot of SSI and transfer compression can be a bit much for that machine, but it got easier than maintaining my nginx config on upgrades.
I happened to have DB logs up and some some queries that weren't me and traced it back here. Good morning, HN.