Concurrent Tautologys (all happening together at once)

I step away from the inkernet for five minutes and of course I miss six million little things.

  • L Sharp .NET is "a powerful Lisp-like scripting language for .NET."
  • Chickenfoot is "a Firefox extension that puts a programming environment in the browser's sidebar ... a superset of Javascript that includes special functions specific to web tasks." (meanwhile i still haven't gotten dirty with grease monkey...)
  • hAxe is an OO language that can compile to js, flash or server-side byte code on apache webservers. It's strictly typed, but uses type-inference (...not unlike Ruby, F#, Powershell... and C# 3.0 ;-) ) .
  • Livewriter is a microsoft tool for bloggin. Looks buggy for now but bound to be popular later.
  • Marcos Meli seems to have done a nice logo for the larkware 1000 competition.
  • hanselman gets into dynamic languages
  • Eric Sink thinks you might as well get into multi-core programming.

  • Multi-core programming... concurrent programming... It's coming at us from three different directions now:

    1. Your next computer will have 32 or so processors
    2. Your server-side code may get to execute across hundreds or thousands of machines
    3. Your ajaxian scripts could share their processing load over hundreds of zombie client machines

    (Yeh, okay, one of those is pure sci-fi)

    On J.Spolsky's advice I read a lot of steve yegge stuff recently (particularly here and here), wherein he discusses the sort of problems you have at a server-side monster like Amazon. He keeps coming back to functional programming. (Lisp in particular, for him.)

    The new client-side multi-core scenario is also tilted toward functional programming.

    To that end, and of course by popular demand, the next 3 minute tutorial will be on F#. It's taken me a lot longer than three minutes to write of course, and it isn't ready yet. But it will be soon enough.

    Meanwhile, here's a quote that keeps running around in my head.... Wirth's Law:

    "Software gets slower faster than hardware gets faster."

    solve: one squared plus two squared plus three squared plus four squared equals three cubed plus three.


    I'm currently writing a book about how to build your first product. If you want to build your first product, please sign up to be notified when the book is available.

    (By the way, I read every comment and often respond.)

    Your comment, please?

    Your Name
    Your Url (optional)
    Note: I may edit, reuse or delete your comment. Don't be mean.