I've been planning to learn some Go for a while now. A friend of mine loves it and takes every opportunity he has to get me to try it. I finally got to try it out and I'm really loving it. One of the courses I'm taking right now is Operating Systems. It has significantly less to do with operating systems than it has to do with learning about deadlocks and synchronization in C. One of the problems we explored was the producer/consumer problem. I decided to write a solution to this problem in both C and Go and compare them.
What if you didn't have to copy over assets between projects every time you wanted consistency? I learned a neat little trick that lets you package assets away into a Gem that can be bundled with any number of Rails applications.