Rackspace wants you to learn their cloud andthey are floating the bill. I've been looking at their services and the flexibility is impressive.OnMetal lets you spin up a physical (not virtual) machine that you control down to the metal.RackConnect lets you mix dedicated servers with elastic instances. But it's daunting to know where to start. That's why the new developer+ program is a great opportunity. Rackspace will give you a$50 credit each month for 12 months to spend however you want. Plus, you can ask for help from Rackspace developers during that time. They will help you choose the mix of services you need for your application.
Thanks, Rackspace, for supporting the Clojure Gazette. Please gosign up for developer+. Put those credits to work!
I recently found this library for pretty printing values at the console. It uses colors, which can help your eye follow the structure of the data printed. It also fills the console horizontally more than clojure.pprint/pprint does. I'm still experimenting with it but I thought I'd share it. DISCUSS
Clojure/conj, the main Clojure conference, is trying to increase the diversity of their attendees. They are offering grants (free ticket and maybe travel assistance) to people based on need and impact on diversity. If it can mean the difference between not attending and attending for you or someone you know, go read about it, sign up, and pass it along. DISCUSS
It's always nice to hear someone from the Clojure community I've followed online featured outside of the Clojure-sphere. This is a great interview, which talks about language design, software business, and where Clojure falls on the late-/early-binding spectrum. DISCUSS
A talk given to LispNYC explaining Category Theory. It's kind of math heavy in the middle, but the beginning and ending convinced me of the importance of category theory in my life. DISCUSS
A friendly if somewhat painful reminder of the leaks in our abstractions. From Garbage Collection pauses to thread affinity, this talk will convince you of the importance of understanding the performance implications of the whole stack. DISCUSS
