aschroder

you could generalize this to crowdsourcing non-tech founders - call it kickstartup.com.

I've been reading about Go a lot lately, starting with Effective Go, and now the tutorial book Learning Go. (and periodically referring to the FAQ when I'm stumped by design decisions)

It's been enjoyable learning it, though I'm yet to write any code in anger with Go. I find some of the concepts around concurrency and OO design have really made me think about the way I write in other languages.

One thing I cannot quite make sense of though is the treatment of errors/exceptions. This article says: "Exceptions make it too easy to ignore them rather than handle them, passing the buck up the call stack.."

But the example given seems to me to do exactly that:

if err != nil { return err }

Worse still if you forget to do something with err, or don't handle a specific err !=nil situation, it seems easy for control to flow past the error handling and into code that expects no errors.

Are there small, easily understood open source projects written in Go, that would provide tangible examples of the benefit of this error handling approach?

The learning materials thus far have not really convinced me, maybe code in the wild would.

I think we can have an 'Open Twitter' without anyone needing to fund it, or own it, or monetize it.

1 to Many short messages are a powerful concept, but as with email - a spec is all we need.

In a nutshell: we define a layer on top of email and mailing lists for short broadcast messages and discovery.

I jotted down my rambling, incoherent thoughts on the subject here: http://www.aschroder.com/2012/07/an-open-twitter-like-networ...