Windows 8: Life in a post .NET world – speak your brains TODAY
Live chat at 2pm BST today
Live Chat Back in 2000, when Bill Gates launched .NET, he likened the shift to the dramatic move from MS-DOS to Windows, as it ushered in an era of distributed computing – for Windows.
.NET became Microsoft’s desktop and server programming story for a decade.
Twelve years on Gates is gone, but his CEO replacement Steve Ballmer reckons Windows 8 is his company’s riskiest bet. Windows 8 introduces a brand-new programming framework, WinRT, geared towards touch input instead of mouse, and cloud download rather than CD install.
Join your fellow Reg readers with Mary-Jo Foley, Tim Anderson and careers man Dom Connor for two one-hour-long Live Chats talking about ModernUI, building for Windows 8 and 9, and the fallout on skills and training.
Our first Live Chat takes place today at 13.00 GMT (14.00 BST, 9.00 ET, 6.00 Pacific) and will dive into programming – .NET versus WinRT. Our follow-up is on 28 September at the same time and will see Dom Connor weigh in on skills – where in the real world can you use your Windows 8 chops in a .NET world?
Today's Live Chat is now finished, but you can carry on talking in our special Living in a post .net world Forum here.
There is no Vs
.net and winRT are not in competition - winRT is a replacement for the ageing WIn32 API (pinvoke etc)
Is this about language or about control?
I think the whole thing runs much deeper than most people care to realize.
First of all; the whole suggestion of a "post .NET world" is preposterous. Because what exactly is WinRT? Basically its a set of Windows 8 APIs, just like the current API ("Windows API" also called "Win32 API") is available on Windows 7 and Vista. Also from .NET, so what's the issue here?
But the reason I call this preposterous is not so much because of the obvious above. Has the author already forgotten about Windows Server 2012? By default this installs in a 'core mode' thus leaving only a command line based console. Administration is done through the Remote Server Administration Tools ("RSAT") and/or... Windows PowerShell. This is Microsoft's "new" de-facto administration tool. And guess what; it sits completely on the .NET framework. PowerShell is what eventually got me to grab a version of the Express versions of Visual Studio for VB.NET and C#.NET.
I think language access is the least bit to be concerned about. When it comes to the influence of the new TIFKAM environment I have much bigger concerns: An immense decrease in control. On Windows 7 I can basically install and use whatever I want. On a TIFKAM based environment I can only use whatever Microsoft provides me with in their marketplace. Thus effectively generating an environment for them to rule out any players which they don't like.
Office 8 is fully TIFKAM integrated. Do you really think that should the OpenOffice people ever step onto the TIFKAM bandwagon and produce a TIFKAM enabled version of their Office environment, that it would find its way onto the Microsoft marketplace? I sincerely doubt that.
THAT is in my opinion the real danger of the whole Windows 8 doctrine. Its not a change of development, its not so much an issue of being forced onto a touch-based user interface which should also be pushed down the throats of the desktop users. No, in my opinion this runs much deeper and seems to be more sinister ("seems to be" because at this point I can obviously not state that MS would actually ban programs such as OpenOffice, but they do create the environment which would allow them to).
Don't worry about languages, worry about being forced into a Microsoft dominated and controlled environment instead. Please note that I'm not suggesting that such an environment would be "bad" or "evil" perse, not my words. But I do state that such an environment could easily be (ab)used to do exactly that.
I think "post .NET world" is a very misleading headline.
What do you think all these Windows 8 apps will be talking to? It'll be cloud services, and if you're a Microsoft shop they will be written in .NET as WebAPI, web services and perhaps standard ASP.NET applications.