Scott Dorman

ephemeral segment

  Home  |   Contact  |   Syndication    |   Login
  603 Posts | 10 Stories | 862 Comments | 51 Trackbacks

News


Post Categories

Image Galleries


Microsoft Store


Creative Commons License



Locations of visitors to this page

Subscribers to this feed

TwitterCounter for @sdorman

View blog authority

Add to Technorati Favorites

Windows Live Alerts

AddThis Social Bookmark Button

LinkedIn profile

Community Credit profile

The Code Project

Follow me on Twitter

Get Free Shots from Snap.com

Community Credit Hall of Fame

Get Feedghost

Xobni outlook add-in for your inbox



Support This Site

Tag Cloud


Article Categories

Archives

Post Categories

Image Galleries

I recently came across the blog of Patrick Dussud, who is the lead architect of the CLR/UIFX group. His first (and currently only post) discusses his role in the birth of the .NET CLR. There is a link to a mailing list archive that also gives some more background.

In a nutshell, the CLR was born out of the COM+ team, created by merging the MTS and COM teams, and some of the people from the JVM team. The COM+ team was working on the next generation of COM, then called COM 2.0 and the JVM guys were realizing that the JVM was not going to give them the support for other languages and the flexibility they were looking for. Combine this with disagreements on some fundamental technology issues, such as object management and garbage collection, and you end up with two teams: COM+ and CLR.

The CLR team was also eventually joined by people from other Microsoft teams, including some of the C++ teams, which helped with the evolution of the IL instruction set, which is based on the Microsoft p-Code instruction set introduced in MSVC 5.0.

Perhaps the most interesting aspect of this is that the initial architecture and prototype for the Garbage Collector was written first in Common Lisp. Unfortunately, Patrick doesn't give a reason for this.

posted on Monday, November 27, 2006 1:37 PM