On Mar 29, 2013, at 03:44, Marko Topolnik wrote: > Yes, you are involving Clojure startup here, which turns the tables > altogether. This is far more work than just Java startup: all the > namespaces must be initialized: all their def'd values calculated > at runtime and assigned. Some of these may involve quite heavyweight > service startup. This is the real issue in the Clojure startup story: > it is not aggressively optimized towards zero startup time. It is a > problem that carries over to other underlying implementations.
So, a naive question. How much of this work could be pre-calculated and/or deferred until the values are needed? -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume r...@cfcl.com http://www.cfcl.com/rdm/weblog +1 650-873-7841 Software system design, development, and documentation -- -- 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/groups/opt_out.
