Episodes 5-10 of the podcast "Clojure in Product: Would you do it again?" highlight the real-world challenges faced by teams using Clojure as they grow. Leaders from companies like CyCognito and Mobot share insights into the evolving dynamics that come with scaling technologies. While Clojure offers stability and performance, developers express career anxieties due to concerns about not being updated with trending technologies like JavaScript. Conversations indicate a trend where teams are exploring migration from Clojure to other languages such as TypeScript for better hiring and skill-set alignment in the competitive job market.
At CyCognito, Yehonathan Sharvit's team built their cybersecurity platform almost entirely in Clojure, handling millions of events per second while mapping digital assets for major enterprises. But success brought unexpected team dynamics. "I think the majority of the developers don't really like Clojure," Sharvit admits candidly. The issue wasn't technical capability - it was career anxiety. Some developers worried about marketability: "If I want to join another company, I won't be aware of the latest JavaScript, React, Webpack modules."
Several teams found themselves considering moves away from Clojure, offering valuable insights into when and why such decisions emerge. CyCognito migrated parts of its system to TypeScript, not due to technical limitations, but rather due to organizational concerns about hiring and expertise retention.
Jereme Corrado at Mobot faced similar pressures during their Series A funding round: "Should we hang up the ClojureScript-based stuff? The concern was about being competitive in hiring" which underscores the shifting priorities experienced by teams striving for growth.
Collection
[
|
...
]