Today in the Intertweets (Nov 9th Ed.)

  • Tail recursion and function composition (here, via @jneira) — Building recursive data structures by recursively composing anonymous functions… er, did I get this one right?
  • Shuffling cards with Clojure (here, via @s_e_t_h) — the title says it all. It is a good post if you want to show someone foreign to lisp how symbolic manipulation and recursion work…
  • Do all God’s chillun have to be writing their web code in Erlang or Haskell or Clojure? (here, via @timbray) — The article explores the evolution of Cloud Computing in their use of multicore and postulates that GAE and Azure will have to eventually provide access to multicore capabilities in their clouds (for example allowing new threads to be created). This will give way to languages like Clojure, Haskell or Erlang.
  • Stopping Times and Laziness (here, via @kotarak) — how to know when it is possible to write some code to be fully lazy
  • Tweaking Clojure (here, via @tiagoantao) — did you know that if you don’t like Clojure’s core libraries, you can rewrite them?
Share this post:
  • Twitter
  • RSS
  • email
  • Reddit
  • Digg
  • FriendFeed
  • Print
  • HackerNews
  • Mixx
  • Google Bookmarks
  • DZone
  • LinkedIn
  • Posterous
  • StumbleUpon
  • Suggest to Techmeme via Twitter
  • Technorati
  • Facebook
  • Tumblr

3 Comments to “Today in the Intertweets (Nov 9th Ed.)”

  1. Phil 10 November 2009 at 11:41 am #

    Thanks for putting together all these links.

    Just a hint, if you make the actual link text the title of the page you’re linking to rather than creating a separate “here” element for the link, it helps crawlers know what’s going on and also eases targeting the links via keyboard-driven browsers. As Strunk and White would say, “omit needless words.”

    • tbatchelli 10 November 2009 at 1:28 pm #

      Hi, thanks for the tip! I guess I wanted to remove some clutter, since in the theme that I am using the links are too big. But your point is taken and I will fix it.

  2. [...] mini blog on poker and #clojure (here, via @s_e_t_h) — this is a followup of a previous article that we referenced a few days ago. The code can now be found in [...]


Leave a Reply