Collaborative articulation of how abstraction and language is employed in the computational manifestation of numbers -- including analysis of the role of syntax, semantics, and meaning in the specification and use of software interfaces.

- Archives - 2004-05-30 2004-06-06 2004-06-13 2004-06-27 2004-08-22 2004-08-29 2004-10-03 2004-12-05 2005-01-23 2005-06-19 2005-08-14 2005-10-09 2006-01-01 2006-02-05 2006-02-12 2006-07-09 2006-07-16 2006-07-30 2006-08-06 2006-08-20 2006-10-08 2006-10-22 2006-10-29 2006-11-26 2007-04-29 2007-11-04 2007-11-11 2007-11-18 2008-01-06 2008-01-13 2008-01-27 2008-02-10 2008-02-24 2008-05-04 2008-05-25 2008-06-08 2008-06-15 2009-06-21 2009-11-08 2010-04-25


Blog Feed

Recent Items
 
Miser Project: Repaving Kick-Off
 
Hark! Is That an Idiom That I See Before Me?
 
Whither Peano?
 
Miser Hacks II: A Hole to Bind Them
 
Petzold Annotates Turing!
 
Hazard Warning: Much Site Breakage I’ve just notic...
 
Tweaking Technorati
 
... feeling unlucky ...
 
Hanging by a Branch
 
Stepping Off the Edge

  

visits to Miser Project pages

The nfoCentrale Blog Conclave
 
Millennia Antica: The Kiln Sitter's Diary
 
nfoWorks: Pursuing Harmony
 
Numbering Peano
 
Orcmid's Lair
 
Orcmid's Live Hideout
 
Prof. von Clueless in the Blunder Dome
 
Spanner Wingnut's Muddleware Lab (experimental)

nfoCentrale Associated Sites
 
DMA: The Document Management Alliance
 
DMware: Document Management Interoperability Exchange
 
Millennia Antica Pottery
 
The Miser Project
 
nfoCentrale: the Anchor Site
 
nfoWare: Information Processing Technology
 
nfoWorks: Tools for Document Interoperability
 
NuovoDoc: Design for Document System Interoperability
 
ODMA Interoperability Exchange
 
Orcmid's Lair
 
TROST: Open-System Trustworthiness

 

2007-11-14: SeaFunc Meet-Up

Four of us turned up for the Wednesday, November 14 meeting of SeaFunc, the Seattle Functional Programming informality.  I was here because I said I would.  Just in case no one bested the rainy evening, I brought my laptop and started composing some blog posts (including this one).

Daniel, Stephen, and Nico showed up near 8pm and we jawed until 10pm.  Nico is the second person at a SeaFunc meeting that owns a Symbolics Lisp machine.  He talked a little about his efforts to install a larger hard drive and create a clean base system.  Apparently there is a lot of source code available (in Common Lisp) and Nico wants to learn from it.  There was some discussion of the power of the IDE and interest in how it might contrast with Smalltalk.

Daniel and Stephen are both with Microsoft.  Daniel and I ended up talking about functional-programming a bit and he explained the trampoline idea to me (since I am interested in Henry Baker's Cheney Copy on the run-time stack technique).  We managed to include discussion of the One Laptop per Child machine (XO), WHS, Windows Live Services (and the webcasts I've been watching).

I didn't take any photographs.  I was having too much fun jabbering.  As recompense I offer the following tidbits:

• In the November 14 issue of the Dr. Dobb's Report newsletter (don't know that it appears on the web), editor Jonathan Erickson leads off with "Functional Languages: Into the Real World."  The signal, to Erickson, is the announcement that Microsoft F# is to "become a first-class citizen of .NET and run on the Common Language Runtime."  Jonathan provides a link to the John Hughes paper, "Why Functional Programming Matters."
     
• As evidence of Microsoft's intention, Don Syme of Microsoft Research Cambridge just posted his welcome to Luke Hoban, the Program Manager for F#.  Although no promises have been made, it is useful to know that Luke was involved in the creation of C# 2005 Express Edition.
   
• Over on hubFS, the forum for F#, there is regular discussion and advice on running F# on Mono.  That means it should not be difficult to have F# (and Moonlight, the Mono counterpart to Silverlight) running on XO.  You knew I'd end up here, right?

¶ posted by orcmid at 11/15/2007 10:42:00 PM

  <$BlogBacklinkTitle$>  

<$BlogBacklinkSnippet$>
posted by <$BlogBacklinkAuthor$> at <$BlogBacklinkDateTime$>