On Friday, January 25, 2013 6:12:07 AM UTC+1, Mikera wrote: > > A natively compiled Clojure would be very very interesting (perhaps > targeting LLVM?) > > However it would also be very hard to implement. Clojure depends on a lot > of features provided by the JVM (JIT compilation, interop with Java > libraries, garbage collection being the most significant ones). It would be > very hard to reimplement all of these from the ground up. The JVM is > already a very good host platform, why fix something that isn't broken? >
What about native ClojuresScript? It doesn't have to implement everything Clojure have already, and many people could consider it good enough alternative to Clojure. I could personally live without runtime macros and eval if it would gain me small and performant native executable. > Arguably the effort would be better spend improving the JVM with extra > features that would help Clojure (e.g. TCO). > > On Tuesday, 22 January 2013 00:29:54 UTC+8, octopusgrabbus wrote: >> >> I use Clojure primarily as a very reliable tool to aid in data >> transformations, that is taking data in one application's database and >> transforming it into the format needed for another applications' database. >> >> So, my question is would a natively compiled Clojure make sense or turn >> the language into something that was not intended? In almost all instances >> I have not found a problem with Clojure's execution speed so my question is >> not about pro or anti Java. >> >> Thanks. >> > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
