disclojure
  • home
  • latest
  • archive
  • follow
  • subscribe

This weekend in the Intertweets (Sept 25th Ed)

  • Changes to Cascade, and a cautionary tale about defrecord (via @yueliufeeds) -- This article is an update on cascade, which basically now it is using Ring/Compojure instead of providing similar functionality. The author also comments on one little known fact about records in clojure and name clashing.
  • Wow... Storm is the most watched Java, Scala, or Clojure project on GitHub (via @nathanmarz) -- At the time of this writing, this meant 1532 watchers.
  • Clojure 1.3 is officially released! (via @redinger) -- You probably want to read the release notes if you don't know what's new already. Get it while it's hot!
  • Stunned again by the #clojure community: @ambrosebs will be traveling from AUS to USA for the 2011 Conj, thanks to you. Details coming soon. (via @cemerick) -- Woo hoo! Pats on the back all around :)
    • Overtone 0.4.0 has been released with full support for Clojure 1.3 (via @Overtone) -- And so it begins...
    • And hot on the tails of the Clojure 1.3 release - ClojureCLR 1.3 has been released! (via @redinger)
  • Miss out on registering for the Clojure/conj? Join our waiting list to be notified when spots open (via @clojure_conj) -- In other words, if you haven't got your ticket yet, tough luck.
  • Once-only evaluation for Clojure macros (via @jneira) -- If you use the same parameter more than once in a macro definition, and when using this macro you pass as a parameter a function call, and if this function call has side effects, then your macro might have unexpected behavior, as the function will be called more than once. This article proposes one solution.
Tweet this post Follow @disclojure

Back to top

Copyright © 2009-2012 Antoni Batchelli