38 ms·
Frankly, IMHO this combines the worst of two worlds: go's non-lispy syntax and clojure's ... dilatoriness/slowness & fragility of its tooling. I'd much prefer a
by stewbrew 12y ago
Frankly, IMHO this combines the worst of two worlds: go's non-lispy syntax and clojure's ... dilatoriness/slowness & fragility of its tooling. I'd much prefer a clojure (or rather scheme) that compiles to go.