Getting ready for the PDC Panel: Looking Ahead to the Future of the CLR


By far the thing I like most about the PDC is hearing from customers… that means the Q&A part of any presentation is what I find most interesting. So it is no wonder that panels are my favorite format at the PDC… because they are nothing but Q&A… 


 


This year I will be hosting the “Future of the CLR Panel”… I am really looking forward to hearing your questions and comments about the CLR generally and our future direction specifically.


 


I’d love to gather a few questions ahead of time, so comment here or drop me a line with questions or topics you think we should cover.. I will do my best to get them in. 


 


  


 

Comments (4)

  1. kfarmer says:

    Movable methods, such as in http://u.pereslavl.ru/~vadim/MCSharp/docs/about/index.php

    .. I think this would really bind the distributed computing story well.

    Choice types, ala C-omega

    .. If I could define a choice type/discriminated union, and use that as a type parameter in a generic, it would solve a big problem I’m facing in a framework we’re designing on our end.

    Other features: Spec#’s invariants, etc.

  2. kfarmer says:

    re movable methods: so you don’t have to read through it all, the gist is that methods can be marked as movable. When the runtime sees this, it knows that this method can be farmed out to a remote runtime for evaluation. The caller of the method doesn’t notice any difference.

    Essentially, this is runtime support for grid computing. Given the expression trees in C#3, I think this would be very doable. In fact, I see it in much the same light as a database service.

    A database will allow you to pull data down, but is limited in its ad hoc processing. A web service has more processing capability, but it’s not ad hoc. Being able to dynamically generate a process and have it hosted near the data would be a great way to do things. Security would need to be addressed, of course.

    It would also make for an interesting deployment story — deploy to one machine in a group, and it sends processes out to the rest, without having (necessarily) to install each component seperately.

  3. kfarmer says:

    and AOP — you know people are going to ask about that one.

    enough from me, now

  4. Mike Swaim says:

    One of the things mentioned about the benefits of IL is the ability to target the processor that is running the code. (In other words, generate different code on a Pentium M than on a P4.) Any plans to do this?

    Also, some Java bytecode compilers will recompile commonly used routines for better performance. Any chance of something like that showing up in .net? (The Alpha’s FX32 emulator did something like this.)