title: What can you do in 30 lines of Go? Can you create a useful, complete program that demonstrates its features?
body: <p>So, the big buzz in the last few days is <a href="http://golang.org/" rel="noreferrer">Go</a>, the new language from Google. Assuming you're all obsessive programming language geeks like me, you've all downloaded it, built it, and run your "Hello, 世界" program (isn't it nice using a language written by the inventors of UTF-8?). You've all read <a href="http://golang.org/doc/go_tutorial.html" rel="noreferrer">the tutorial</a>, <a href="http://golang.org/doc/effective_go.html" rel="noreferrer">Effective Go</a>, and some of the other docs.</p>
  
  <p>Now, what are you going to do with it?</p>
  
  <p>I'd like to see some demos that show off the power of Go. What can you do in a brief program? Show off your best example code. While the true measure of a language can't really be taken until you've written and maintained a large codebase with a team of many programmers over the course of a project with changing requirements, seeing how much you can do in a limited amount of code does help to demonstrate the expressive power of a language. I'd like to see short, complete programs that truly exercise the unique new features of Go; not just snippets or "Hello, World".</p>
  
  <p>So, post some cool code you've written with Go. Take advantage of its unique features, like its goroutines and channels for concurrency, or its interface based type system. Can you write a primitive chat server, or cool IRC bot? Implement a parallel Mandelbrot set that scales to many cores? Write an interpreter for some tiny language? And can you do it all in 30 lines? </p>
  
  <p>I chose 30 arbitrarily as about as much as you can fit into a Stack Overflow code block without it overflowing and getting a scroll bar; it should be enough to do something interesting without golfing too much, but short enough to keep everyone's attention for a quick demo. For instance, with just a bit of reformatting, the example <a href="http://golang.org/doc/effective_go.html#web_server" rel="noreferrer">web server</a> should be able to fit (not counting the data).</p>
  
  <p>Show us your Go code!</p>