Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Discussions

Richard Anthony Hein Richard.Hein Stay on Target
  • really microsoft... really?

    @DeathByVisualStudio:  The blog is a blog ... sure we can politely ask the blog owner to put a link in, but seriously, is it that hard to do an actual search for yourself?  There's a ton of links related to Powershell, why should they necessarily have the download as the top link?  Adding "download" to the keywords refines the search, and it seems to be the logical thing to do rather than post to the Coffeehouse complaining that it's hard to find.

    http://search.microsoft.com/results.aspx?form=MSHOME&mkt=en-us&setlang=en-us&q=powershell has the download page as the 3rd link. http://search.microsoft.com/Results.aspx?q=powershell+download&mkt=en-US&FORM=QBME1&l=1&refradio=0 has it as the 1st link.  'Nuff said!

     [Edit:  Removed harsh language.]

  • really microsoft... really?

    @Jaz: Umm, "powershell 2.0 download" ... first link.

  • Channel 9 Live Event

    , Bas wrote

    http://channel9.msdn.com/posts/Join-Us-Tomorrow-For-A-Special-Channel-9-Live-Kinect-Event

    Well, mystery solved. Damn, I'm going to miss it. When will it be available on demand?

     

    , jeffsand wrote

    *snip*

    Yes! Within about 24 hours of this broadcast, all materials will be downloadable on @ch9.

  • "None of us at Microsoft can say anything until //build/ in September."

    @contextfree`:  Point taken, but while the whole package out of the box may be a big deal, all of these things have been possible before and while it's good that things will be easier, what's new enough about all of this to be as big a difference as Windows 3.1 vs. Windows '95?  New APIs that make what was possible before, slightly easier, isn't that big a deal.  Support for ARM, was announced a while ago, and demoed at Mix'11.  Touch isn't new. 

    Why switch the conference from "PDC" to "BUILD"?  There's something going on deeper than what has been announced, otherwise MS devs wouldn't be saying, "None of us at Microsoft can say anything until //build/ in September"; everything you mentioned has already been officially announced (except the new version of COM, AFAIK).  One thing is for sure, I'm going to do my best to make the conference this year.  I'll be sorely dissappointed if things don't pan out along the lines I've predicted.  I've been wrong in the past, however, so I won't be too surprised, either way.

  • "None of us at Microsoft can say anything until //build/ in September."

    Let me also quote from http://research.microsoft.com/en-us/um/people/emeijer/Papers/DemocratizingTheCloudOOPSLA2007.pdf

    "We pick the .NET Common Language Runtime (CLR) as our universal computation model. We prefer, of course, to use the already available CLR implementation on each respective tier: SQLCLR on the data-tier; regular CLR on the middle-tier; and Silverlight for Web-clients, or the regular CLR for desktop clients.  When no CLR is on hand, we use the materials already available in the room. On the data-tier we compile MSIL to SQL. This is the approach currently taken by LINQ-to-SQL and LINQ-to-Entities. On the client-tier we compile MSIL to JavaScript or Flash. This is the approach taken by Volta. The upshot is that we uniformly provide (the illusion of) the .NET platform on each tier, in effect stretching it to cover the Cloud. Application programmers only need to care that they can run MSIL everywhere, not about how this is technically accomplished under the hood."

    I'll point out http://channel9.msdn.com/Blogs/Charles/Erik-Meijer-Democratizing-the-Cloud as well, again, so that those who haven't seen this will see that nearly 5 years has passed and these experimental ideas are ripe for production, IMO.

  • "None of us at Microsoft can say anything until //build/ in September."

    "Our approach means no compromises—you get to use whatever kind of device you prefer to run the apps you love. This is sure to inspire a new generation of modern hardware and software development, improving the experience for PC users around the world." - BUILD

    They are also touting this as the biggest thing since Windows 95.  That's a hard sell.  There has to be a reason, and it's not HTML5/JS.

    @ContextFree: Microsoft already has implemented an IL to JS compiler in Volta.  I tried to find a link, but guess what, all the Volta videos are no longer available.  Strange??  Not really.   However, I'll concede that maybe it's C# to JS ... which Script# already does, but not as deeply.  Also see http://hildr.luminance.org/Platformer/Platformer.html ; there's nothing stopping compilation from one Turing complete runtime to another but imagination, and blood, sweat and tears (and buckets of cash). 

  • "None of us at Microsoft can say anything until //build/ in September."

    I think that BUILD will actually be about the new compiler technology that Bartok and Pheonix research has led to, and not just about Windows 8.  I believe that Microsoft doesn't really have much intention to make tools to directly manipulate HTML/JS, but will extend existing tools, in particular Blend and VS to compile down to HTML/JS - and run on a JS based .NET Framework. 

    To facilitate that effort, I think that they will be announcing IL to Javascript compilation, XAML (Silverlight and/or WPF) to HTML/CSS/JS compilation, and a new way of looking at .NET as a whole.  The CLR will still produce IL, but that will be fed into Bartok/Pheonix and allow compilation to JS (as a new, or more properly, a secondary IL), with a JS version of the .NET Framework.  Microsoft is probably sick of trying to get the CLR on every device and will thus have the rest of the market build CLRs for them - via JS interpretors.  This strategy will truly make JS the IL of the web and anything that runs Javascript, will become a CLR. 

    I also think we'll be able to target either CLR=>IL=>JS or CLR=>Bartok/Pheonix=>Native.  I think that there will also be a way to compile parts of an application from CLR=>IL=>JS and parts to native.  As the Windows 8 leaks have demonstrated, the Windows 8 sample applications have HTML/JS UIs, that interop with the Windows Runtime dlls by marshalling JSON through MSHelpUI.dll to other dlls, which appear to be compiled from C# into native dlls.  It also appears that the UI can either be targeted to be output as HTML/JS or XAML/IL, or native Win32.  

    In summary, I think a lot of the ideas of Pheonix, Volta, Bartok etc..., have made it into the Windows 8 stack and rather than moving backwards and abandoning .NET, which is kind of what the HTML/JS push seems like, this is actually a move to make the dream of a true CLR come true.  Microsoft has thus realized that there are only two real CLRs in the world today - native and Javascript, and are going to make sure that the .NET strategy shifts towards having a compiler framework that allows production of code for those CLRs, instead of trying to make the world adopt their CLR.  All the effort that goes into producing various versions of the CLR (and DLR) is better spent making backends for the Pheonix pipeline to target the native or JS based runtimes which other people are building already.

    Of course, I have absolutely no idea if any of this is correct.

  • On the plus side

    @felix9: +1 ... Cool

  • Azure Map Reduce

    @Nabarun:  Hadoop will work on Azure:  http://blogs.msdn.com/b/mariok/archive/2011/05/11/hadoop-in-azure.aspx

     

     

  • Volta - Dead or Alive?

    @fanbaby:  Only in a limited sense where there is compilation/interpretation to JS, but the overarching theme was "democratizing the cloud", by abstracting away notions like tiers and location away.  Rx is a piece of the puzzle by providing an abstraction over push-based streams, and thus allowing LINQ to be used to compose asynchronous operations.  Volta seems to have exposed the need for things like Rx, but I'm just guessing at how it evolved.