Hazy Shade of Fall in LA

I flew into LA late last night from Portland for the Microsoft PDC conference. My outbound flight was
delayed due to slowdowns in the LA area from the fires, and I didn’t get into
LAX until around 1:30am. The night-time descent through the valley and into LA
was surreal – we could see the glow from the Simi Valley fires, and the smoke
permeated the cabin so much that my eyes watered. I’m glad I’ll be spending
most of my time indoors here – the outside world is hazy and the smell of
smoke and ash is pervasive.

I lived in LA for a short while back in the early 90s, and one distinct memory
of the place is a sequence of one natural disaster after another. This is a
hardluck state.

Don Box on Indigo

I’m sitting in a great talk by Don Box on Indigo, the new model and
implementation for distributed computing from Microsoft. Don refers back to
the software integrated circuit (IC) analogy for object oriented computing,
which has its roots in Brad Cox’s work on
Objective-C back in the 80s. Great metaphor, but even in the world of hardware
that model never worked – ICs tend to be too coupled to other components and
are actually soldered on the board to build a subsystem like a video card or
motherboard. It hasn’t worked all that well in the software world either –
DCOM, CORBA, RMI, etc. are much harder to use than they should be. And
according to Don it is about boundaries – distributed object computing is not
respectful of boundaries and results in tightly coupled, difficult to evolve
applications.

Don summarized his position with these tenets:

  1. Distributed Objects won’t work. We’ve tried to make it work, boundaries need to be explicit.
  2. Services are autonomous. Independent versioning, deployment, and security.
  3. Share schema, not class. Integration is based on message formats and exchange patterns, not classes and objects. As soon as we start stretching the wire, and allowing services to become autonomous, we have no idea what runtime, what runtime version, etc. Its all about boundaries.
  4. Policy-based compatibility. We make explicit assertions about capabilities.

What is Indigo? A collection of .NET assemblies (DLLs). The Indigo
architecture consists of a Service Model, Messaging Services, System Services,
Connectors, and Hosting Environments. Indigo makes service orientation more
explicit, makes boundaries more obvious.

using System.ServiceModel;  

 [Service] class MyService  
 {  
    [ServiceMethod]  
    void f() {}  

    public void g() {}  
 }

If I’m talking to the class from within the same app (CLR), I can call g() on
this class. If I’m talking to my class in a service-oriented way, the only way
to access is through f(), and Indigo will sit in the middle as an interception
point. I can’t even call f() directly – it is implicitly private.

Indigo is also about unification of remoting models between ASMX, .NET
remoting, and Enterprise Services. Indigo is also about interoperability, and
WSE is an intermediate step along the way. Once Indigo is out the door, WSE
will evolve to track the protocol evolution for Indigo users, just as it does
the same for ASMX users today.

The penalty for using Indigo and service-oriented computing in general should
be low. They are working extremely hard on performance and, to quote Don,
“miniaturization” of this general concept.

Preparing for Indigo:

  • Use ASMX today – the closest thing to the TRUTH today.
  • Use .NET Enterprise Services within your service if you need ES functionality or if you need fast/secure intra-farm ORPC. FYI, this is where Corillian is today, and right where we should be.
  • Use .NET remoting within your service.

Yet Another Blog About Games

Looks like this is really catching on. Great to see other people joining the
fray and sharing session reports, reviews, and other thoughts on gaming.
Tolen Dante has just started his weblog.

Update: Tolen moved his blog to a new site with RSS feeds.

Jacob’s Birthday Party

Well, I’m only about 2 weeks late in posting this one. We hosted a mystery
party for Jacob and a few friends two Saturdays ago – sort of like a “How to
Host a Murder” game but for kids. The theme was western, and we asked the
party goers to dress the part. Jacob only invited boys, and there were a few
girl parts, so we had to improvise. Part of the improvisation was having
Matthew dress up as a girl – and Grandma was more than happy to help out.
Check out the results for yourself; should make for some great blackmail
material somewhere down the road.

The party went very well – we mixed in some games with the mystery puzzle, and
everyone played their parts. Jacob is nine now, and thought it seems cliche to
say that I can’t believe how fast he is growing up, well, I can’t believe how
fast he is growing up!

Yesterday, Jacob played in his last football game of the season, and his team
finished 8-0. Not a bad season! Jacob played out the year as the starting
center, and was getting much more playing time on defense as well. Julie and I
are sold on the value of this program for Jacob, and we are eager to sign up
Matthew as soon as he is old enough.

Picked Up an iBook

I found a good price on a used iBook here in town, so Jacob and I went to check it out on Saturday morning before his football game. There were a few reasons for picking this up:

  • A good platform for experimenting with Rotor and Mono.
  • OSX / Panther / Jaguar just seemed too cool to miss out on.
  • I think it will be a better home for my iPod link and iTunes.
  • I wanted a personal laptop for travel, especially for important tasks like playing DVDs for the boys on road trips.

So far I love it. I’m playing with some different software configurations
(browser, office tools, etc.) to see what works best. One disappointment –
OpenOffice supposedly works, but isn’t a native
Mac OSX application (it runs under X11). It also didn’t work in a turnkey
maner, probably because I’m not using Darwin as my X11 server.