Joe Duffy joins the CLR team


I have been negligent in announcing that Joe Duffy recently joined the CLR team to focus on bringing WinFX together.  As you can see from his blog, he is starting to settle in.  What would you like to see Joe take on in the WinFX, Design Guidelines, managed code space?   I can’t promise I will do it, but I always like to hear your thoughts.


 


As an aside, I think it is amazing how blogs are changing the way this industry works… Even though I was not hiring for a blog-for-a-living kind of job (a la Scoble), Joe and I still hooked up because of blogs.  He already knew a ton about the kind of job he would be taking and I knew about the kind of person I was hiring.  Interesting to think about how your blog is a living resume for you… what does your blog say about you?

Comments (5)

  1. Sathyaish Chakravarthy says:

    My hearty congratulations to Joe, who joined the CLR team. I expect to see all of you there, at Redmond, soon.

  2. Keith Hill says:

    Could Joe (or someone) look at some of the duplication going on WRT support for the VB My classes. System.IO.FileSystem has about two new, interesting members (CopyDirectory and GetRelativePath) and everything else is duplicated functionality. Even the two new members should be put else where. CopyDirectory should be a static under System.IO.Directory and GetRelativePath should be a static under System.IO.Path. I find just about everything else in System.IO.FileSystem redundant and confusing.

    With the core of .NET (System.*) becoming the core of WinFX a.k.a. the next Windows API, I expect to see some more separation between OS API and specific language runtime libraries. That is, if the VB team wants to add "training wheel" classes then they should do it in Microsoft.VisualBasic.* and not in System.*. Please try to keep the future OS API surface area as small as possible.

    BTW, System.Text.Parsing.TextFieldParser is another VB addition were I see limited appeal. I’d rather see System.Text.Parsing.StringTokenizer but that’s another story for another day. 🙂

  3. Brad Abrams says:

    Funny you should mention that Keith. I already have someone looking at that and you should expect some good things in Beta2… Your vision of the world is pretty close to mine…

  4. Keith Hil says:

    That’s good to hear! Thanks.

  5. Keith Hil says:

    Another VB My classes duplicate that I missed is System.IO.SpecialDirectories. This class pales in comparison to Environment.GetFolderPath(). Now you could argue that perhaps this functionality should be in System.IO but SpecialDirectories as it stands now is pretty lame.