Windows 8: .NET Versus HTML5 Metro App Development

An anonymous reader writes "Will Microsoft take advantage of .NET's Java-like CIL and allow .NET code to run on Windows 8, or force developers to switch to HTML5 Metro apps instead for porting apps to Windows 8? This article brings up important insights into both paradigms' advantages and disadvantages, and even correlates the options with Microsoft's past NT-era support of MIPS and PPC, as well as Windows CE's way of supporting embedded architectures."

Re:Idiot

[Anonymous Coward]

Now who's the idiot? CLR is a calcium, lime, and rust cleaner. It doesn't compile anything!

Re:Then you can be the smartest guru on the cinder

[Rogerborg]

Yup, just more Microsoft word-spooge onto the faces of the developmentally naive.

Joke going around the office: Microsoft buys Yammer, renames it SharePoint Cloud Server 2012 Mobile Enterprise Social Networking Edition. - Gene Smith, Twitter

Someone left an MSDN magazine lying around in work. It had an article titled something like "Leveraging code re-use via multiparadigmatic metaprogramming lambda expressions". After some head scratching, I eventually figured out that they were talking about implementing macros in C#.

Re:Idiot

[Anonymous Coward]

He didn't mean Command Line Interface.

Common Language Infrastructure [wikipedia.org]

The Common Language Infrastructure (CLI) is an open specification developed by Microsoft and standardized by ISO[1] and ECMA[2] that describes the executable code and runtime environment that form the core of the Microsoft .NET Framework and the free and open source implementations Mono and Portable.NET. The specification defines an environment that allows multiple high-level languages to be used on different computer platforms without being rewritten for specific architectures.

Complete moron still applies, I think.