4 ms·

clojure on the jvm has much better performance than ruby, but for my small side projects, that doesn’t matter. I guess I was trying to describe the frustration

by swlkr 4y ago

clojure on the jvm has much better performance than ruby, but for my small side projects, that doesn’t matter. I guess I was trying to describe the frustration of switching languages and ecosystems while also trying to ship, thought I could do it, but I couldn’t. I suppose I would have had a much better time and stayed in C-land (and gotten much better performance) if I had tried golang instead of clojure.

Tainnor 4y ago
If you have deadlines and can't afford being "bad" at something for a while then, yes, learning new technologies or ecosystems might not be a wise choice. I think that's independent of what those technologies are. I switched to the JVM because I was annoyed enough at the things I had to deal with in Ruby that learning how to do things in a new way was worth it for me in the long run. > I suppose I would have had a much better time and stayed in C-land (and gotten much better performance) if I had tried golang instead of clojure. But Go is a completely different language than Clojure? By what criterion are you deciding which language to focus on? Mostly I'd think that people who choose Clojure do so because they want to use a homoiconic, dynamically typed, functional programming language and not something that looks a lot like a cleaned-up C.
- swlkr 4y ago
  These days I care less about how the language looks and more about the development/deployment experience, and how much memory it’s going to take on a VPS, since that’s the primary thing driving VPS costs. Ruby (and rails) for web applications is very hard to beat ergonomically. Go also feels this way to me, the development experience is very simple, deployment is even easier than ruby/rack (assuming no docker), and you get the added bonus of using a lot less memory on the server.

4 ms·

clojure on the jvm has much better performance than ruby, but for my small side projects, that doesn’t matter. I guess I was trying to describe the frustration

by swlkr 4y ago

Tainnor 4y ago
If you have deadlines and can't afford being "bad" at something for a while then, yes, learning new technologies or ecosystems might not be a wise choice. I think that's independent of what those technologies are. I switched to the JVM because I was annoyed enough at the things I had to deal with in Ruby that learning how to do things in a new way was worth it for me in the long run. > I suppose I would have had a much better time and stayed in C-land (and gotten much better performance) if I had tried golang instead of clojure. But Go is a completely different language than Clojure? By what criterion are you deciding which language to focus on? Mostly I'd think that people who choose Clojure do so because they want to use a homoiconic, dynamically typed, functional programming language and not something that looks a lot like a cleaned-up C.
- swlkr 4y ago
  These days I care less about how the language looks and more about the development/deployment experience, and how much memory it’s going to take on a VPS, since that’s the primary thing driving VPS costs. Ruby (and rails) for web applications is very hard to beat ergonomically. Go also feels this way to me, the development experience is very simple, deployment is even easier than ruby/rack (assuming no docker), and you get the added bonus of using a lot less memory on the server.