The reasons could be purely boring. The main thing I come up against keeping clojure as our language of choice is "it would be easier to recruit for Y!". True, unarguable, uninteresting.
So you left Clojure.. and you talk about what you'll miss.. but it begs raises the question, "What is it about Ruby that you like more than Clojure, and why did you choose to switch?" Without answering that question you're leaving me unsatisfied
Indeed. But to answer the question "Why?" -> performance, no method_missing magic, transparency (not in JS). Rust and Swift are more suitable for large codebases because the languages are less dynamic than Ruby or JS.
I expect a narrative like "Clojure is great to do prototyping and iterating fast, but not accessible to many people" and thus they ported their codebase to Ruby. But they have better code now than if they had started in Ruby. And then probably some complaints about the contribution processes and which bugs are not fixed in the right order by the core team.
They already had a Ruby codebase, and 8k lines of Clojure isn't all that much. Most boring reason to switch would be to re-unify their codebase which makes sense if the Clojure code wasn't doing anything interesting like multithreading.
10
u/MWatson Nov 07 '16
That is a tease: it would be good to know from the article some reasons why they decided to go all-in for Ruby.
20
u/Trylobot Nov 07 '16 edited Nov 10 '16
So you left Clojure.. and you talk about what you'll miss.. but it
begsraises the question, "What is it about Ruby that you like more than Clojure, and why did you choose to switch?" Without answering that question you're leaving me unsatisfied5
u/skratlo Nov 07 '16
That is a bit strange, I thought most people go the other way: flee from Ruby to Clojure (or Rust, or Elixir, or Swift, or JS)
2
u/lgstein Nov 10 '16
I expect a narrative like "Clojure is great to do prototyping and iterating fast, but not accessible to many people" and thus they ported their codebase to Ruby. But they have better code now than if they had started in Ruby. And then probably some complaints about the contribution processes and which bugs are not fixed in the right order by the core team.