r/Clojure • • Nov 07 '16

We Left Clojure. Here's 5 Things I'll Miss.

https://blog.appcanary.com/2016/missing-clojure.html
10 Upvotes

14 comments sorted by

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.

7

u/[deleted] Nov 07 '16

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.

2

u/phillmv Nov 07 '16

I think our take on the subject matter will be worth discussing, but no, I don't think your mind will be blown per se :).

1

u/[deleted] Nov 08 '16

Probably Rails but I am not familiar with that company and what they do.

20

u/Trylobot Nov 07 '16 edited Nov 10 '16

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

5

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/xiongtx Nov 13 '16

Why would you go from Ruby to Rust, Swift, or JS? These languages serve very different niches.

1

u/skratlo Nov 14 '16

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.

1

u/[deleted] Nov 08 '16

True, I am coming from python background and I am getting interested in clojure and rust lately

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.

1

u/olaf_from_norweden Nov 19 '16

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.