3 ms·
Clojure isn't pitched to be a toy language. The sell is that it is making a great many really thoughtful design choices that add up to a pleasant language. The
by roenxi 5y ago
Clojure isn't pitched to be a toy language. The sell is that it is making a great many really thoughtful design choices that add up to a pleasant language.
The reason Clojure Classic is hosted on the JVM is because Rich wanted access to the Java ecosystem (and probably because the JVM is an awesome piece of tech). If ClojureRS follows the same mentality, the point here is someone wants to program in Clojure but have access to the Rust ecosystem.
From this perspective it is clear why they'd avoid taking a small-subset approach with a possible performance hit. This isn't a tour of force showing how great Clojure is & how clever someone is that they can implement it on Rust. The idea is to get work done, using Clojure, which may need access to Rust's libraries. It doesn't need to be elegant, that isn't especially important.
- tko38 5y agoActually as mentioned in another comment, I believe I did at least think about it, even if not for this project. However I believe I went in another direction
- temporallobe 5y agoI appreciate this comment, as it answers the exact question I had in my head. I was actually wondering what the point of implementing a JVM-based language in another language was, but this sums it up nicely. As a Java (and Clojure) developer, Clojure makes perfect sense to me and I love the inteop capabilities because I know the Java ecosystem. ClojureRS would therefore make a lot sense to a Rust developer.