3 ms·
The headline is misleading. He actually built similar products in both Python/Django and Clojure at the same time. He didn't replace one with the other. It's m
by KingMob 9y ago
The headline is misleading. He actually built similar products in both Python/Django and Clojure at the same time. He didn't replace one with the other.
It's mostly a language comparison blog post. "These were the good parts of Clojure, these were the bad parts, etc."
- rlander 9y agoNot really. It was more of a "platform choices" comparison blog post. We're mostly a Django shop, so the Python project began a few months before the Clojure one. We had the feeling that Clojure might be a good fit for a few use cases that we have, especially mobile-focused API backends, so the post is a summary of some of the lessons we learned when using a Clojure web stack instead of Django.