> (i love how supposedly we've come so far with our systems, only to > have them become overly complex. it is to sigh. on the other hand i > guess it is 'job security'.)
Heh, true. Reading articles about JVM tuning reminds me what the "M" stands for -- it's as complicated a topic as optimizing the interface between your code and a real machine. E.g., http://blogs.sun.com/bharath/entry/taming_gc_for_sip_applications http://blog.headius.com/2009/01/my-favorite-hotspot-jvm-flags.html Your point about job security is spot on, though -- every time the topics of VHLLs, autonomic systems, and so on arise, I gently point out that somebody needs to figure out what's going on when they stop working, and the smarter they get, the more fiendish the problems! -- 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
