Sorry if it isn't super highlighted, but if you scroll down a bit, you'll see that I support most languages you'd want to use this for (current notable exceptio

Sorry if it isn't super highlighted, but if you scroll down a bit, you'll see that I support most languages you'd want to use this for (current notable exceptions are Go and Obj-C, the former of which is coming soon). Here's the list: c, c#, c++, clojure, coffeescript, haskell, java, javascript, lua, php, python, ruby, scala, scheme As for your philosophical objection, I think the true value prop of CoderPad is a bit more nuanced than you make it seem, respectfully. The primary benefits as I see them are twofold: 1. The right kind of candidate is wowed. It is a real fish landing back in the ocean moment. "Finally, this works like I've always dreamed it should." You look really sexy administering that interview. 2. It can help you see candidates who have a firm grasp of programming but not quite a great hold on syntax do better. I would argue the former is more important, and CoderPad let's you see them experiment with syntax without having to rack their brains over whether the parameter goes before "do" in ruby.