For a public lib I agree. For commercial software running in foreign systems, its a must. Can't see any company shipping source code in the wild...
I maintain a public lib to do dependency injection (boing), it's callable from Java, I maintain 2 AOT versions (clojure 1.2 and 1.3). It's a bit more management but it's a sums up to maintaining two project.clj and two separate versioning systems. Splitting away the small Java APi as an independent component is a good idea. I'll give it a try in the next release. I could then avoid this little extra work. Luc > Hi Luc, > > Am Donnerstag, 5. April 2012 01:51:25 UTC+2 schrieb Luc: > > > > Agree, I still wonder about the downsides of AOT, comments ? > > > Main downside - especially for an arbitrary library: it locks you down on > the specific clojure version you used for compiling, also the using > project. For a library this is probably a killer argument. AOT should only > be used by applications, I guess. > > And it increases jar size if you send stuff a lot over the wire (probably > not a problem in practice?). > > Meikel > > > -- > 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 -- Softaddicts<lprefonta...@softaddicts.ca> sent by ibisMail! -- 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
