On Sunday, November 4, 2018 at 6:50:19 AM UTC-6, Matching Socks wrote: > > > Reading between the lines, I see a sidelining of AOT compilation. >
In general, I'd say distributing libraries as source has always been preferable and is pretty ubiquitous. I can't think of any library distributed as AOT-only (there are a few contribs that ship an additional aot classifier version of the lib, but that's not the one most people consume). AOT-compiling production apps is common, but that's not typically distributed. Several tools already exist to AOT compile deps.edn projects and people are doing that. In general, I see largely the status quo with deps.edn projects - libs are being distributed source-only (sometimes via git deps instead of an artifact) and apps are still being AOT'ed. The core team continues to talk about ways to make AOT caching more integrated and automatic (there is no reason to AOT-compile the same version of a lib every time you start a Clojure app). And we continue to talk about ways to make loading faster. Not actively working on anything at the moment, but I expect this will bubble up again soon. -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
