This article seems to be pushing Martini, which at first glance looks interesting (though it doesn't appear to have been mentioned on the mailing list even once, so there may be some boosting involved).
There is Revel, but it seems to be getting a bad rap ("non-idiomatic" label used as a stick).
Martini is still young (less than a week) but the core is pretty fleshed out.
No boosting here (I don't even have that many twitter followers). I just put together a framework that doesn't step on your toes and people ate it up :)
I love what I've seen so far. The biggest problem is probably the age. Googling for "go martini json" will not yield results until more users start to talk about it.
Yup. Getting there will take a while. In the meantime I plan on releasing a whole bunch of middleware in the martini-contrib repo and creating more video tutorials on web development in Go.
This appears to be another mechanism to mitigate CSRF vulnerabilities, tailored to a single page app. It is quite similar to, for example, putting a security token into a form that is validated on post. The difference is that it is put into a header. This is probably less secure, in fact, because the token comes straight from the cookie. CSRF tokens are typically generated server side and can thus be made cryptographically strong.
It's funny because the author initially advocates against using cookies because they are susceptible to CSRF attacks, and then immediately suggests using cookies as part of this new scheme (albeit in a different way).
This is a good example of why you shouldn't design your own security system unless you are an expert in security and/or cryptography.
Check the mailing list for this. There wasn't a large amount of discussion about mobile options when I last checked, but one solution seems to be what you've already listed above: Phonegap/Cordova.
Cheating a bit since I didn't read the article, but having been in and out of that world for a number of years, there were always certain types of clients who didn't want to hire a company--they only wanted to deal with individuals, for reasons stated or unstated.
From a different perspective, has anyone ever taken the time to read local health department restaurant inspection reports (if available)?
I assume most people here eat at restaurants without too much concern, but if you ever read the reports, you'll find experienced industry professionals cited for far worse infractions than these.
If I went into an interview and asked why they chose a document-oriented database, and that one in particular, think I'd be popular? (I like to play with new techologies, too, but it seems odd to see it mentioned as a requirement.)
Many job ads are written by HR, based on a list of technologies that developers naively provided them. Some of our job ads have technologies that we briefly used once in an experiment that was never more than 20% complete, while MongoDB (which we use in production) isn't currently listed.3
It's very on-topic, and used to be HN's sweet spot.