future of dot net
-
Specifically, the new Windows 8 interface is a more tile-based interface that relies heavily upon HTML5 and JavaScript. Here's how Julie Larson-Green, Corporate Vice President, Windows Experience described it:
If you are a Windows developer, I'll bet you did: there was little to no mention of .NET technology in the Windows 8 hoopla, and quite a few Windows developers are more than a little angry about the whole thing.
http://forums.silverlight.net/forums/p/230502/562113.aspx[^] http://www.itworld.com/mobile-wireless/171285/parting-linux-and-mono[^] the highly debated, future of dot net. :suss:
"Incorrectly attributing quotes to revered historical figures is the work of fools and gerrymanderers; but hey, that's the internet for you." -- Thomas Jefferson
jgasm wrote:
fparting-linux-and-mono
;P
Good judgment comes from experience, and experience comes from bad judgment. Barry LePatner
-
I feel so old. We went through this whole thing with MFC. Then C++. Then Windows Forms. Then VB6. Then everything else that came after it. All those technologies are alive and well waaaaay after their use-by date. The inertia in businesses to change, and the sheer size of the installed base of these, and all the other technologies, means they won't be dead in a hurry. [Edit: I just need to rant a little more. Just because Microsoft doesn't mention .NET doesn't mean it's dead. They didn't mention C++ either, or MVC, or WCF, or Visual Studio. Nor did they mention installers, file compression or hedgehogs. Why does that mean they'll be nuked? And - and this is the big question - why are we getting hot and bothered by a Linux / mono guy spreading FUD??.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Chris Maunder wrote:
hedgehogs.
Egads! I'm having enough trouble learning C# and SQL Server. Now I've got to learn to make hedgehogs work, too? Does MS Press have a book for that? Oh well, it will probably be easier than getting my front office staff to work. :sigh:
Will Rogers never met me.
-
Specifically, the new Windows 8 interface is a more tile-based interface that relies heavily upon HTML5 and JavaScript. Here's how Julie Larson-Green, Corporate Vice President, Windows Experience described it:
If you are a Windows developer, I'll bet you did: there was little to no mention of .NET technology in the Windows 8 hoopla, and quite a few Windows developers are more than a little angry about the whole thing.
http://forums.silverlight.net/forums/p/230502/562113.aspx[^] http://www.itworld.com/mobile-wireless/171285/parting-linux-and-mono[^] the highly debated, future of dot net. :suss:
"Incorrectly attributing quotes to revered historical figures is the work of fools and gerrymanderers; but hey, that's the internet for you." -- Thomas Jefferson
To be honest, this is complete bollocks. Unadulterated, uninformed crap. .NET is not being dropped. .NET is not being replaced. .NET is likely to form a more integral part of the OS based on a project that's nearing completion called Redhawk. Let me address another thing here which some people just don't seem to understand. The Metro UI is not the only interface you can use for Windows 8. The Aero interface is still going to be available but, as it doesn't work that well for tablets and other none-mouse oriented devices, Metro will be available to use - which is suited to touch devices. I talk about this here[^].
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
It's all relative as the Mayans, and others predicted that Microsoft would be destroyed on Dec. 21 2012 and a new order would take it's place.
"Life can only be understood backwards, but it must be lived forward." Kierkegaard, Søren
Hail god Google
-
rewind 10 years and replace ".Net" with "MFC". nothing lasts forever, except 4:00 meetings.
rewind another 10 years, an there were plentyful programming languages on a variety of operating systems, bring back the good 'old' days.
-
To be honest, this is complete bollocks. Unadulterated, uninformed crap. .NET is not being dropped. .NET is not being replaced. .NET is likely to form a more integral part of the OS based on a project that's nearing completion called Redhawk. Let me address another thing here which some people just don't seem to understand. The Metro UI is not the only interface you can use for Windows 8. The Aero interface is still going to be available but, as it doesn't work that well for tablets and other none-mouse oriented devices, Metro will be available to use - which is suited to touch devices. I talk about this here[^].
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
Plus you could convert your WPF/Winform apps to 'look' like metro styled apps.
-
Don't worry 'bout me, I'm fine and don't even care about the subject you posted, I was concerned 'bout you. After all, if we can't use tags correctly on a website where we communicate between ourselves how we suppose to make complex systems?
Mladen Jankovic wrote:
how we suppose to make complex systems?
Hire Consultant CP Hamsters :thumbsup: :rolleyes:
Steve _________________ I C(++) therefore I am
-
Chris Maunder wrote:
hedgehogs.
Egads! I'm having enough trouble learning C# and SQL Server. Now I've got to learn to make hedgehogs work, too? Does MS Press have a book for that? Oh well, it will probably be easier than getting my front office staff to work. :sigh:
Will Rogers never met me.
We'll start a section when we get enough interest. Relax - we'll have you covered.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
Yes, given how few people are using .NET, and how unsuccessful the platform as been in terms of people taking it up, a lack of .NET code in the core of Windows 8 obviously spells the death of the platform and unemployment for the handful of developers who made the mistake of ever using it.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
I feel so old. We went through this whole thing with MFC. Then C++. Then Windows Forms. Then VB6. Then everything else that came after it. All those technologies are alive and well waaaaay after their use-by date. The inertia in businesses to change, and the sheer size of the installed base of these, and all the other technologies, means they won't be dead in a hurry. [Edit: I just need to rant a little more. Just because Microsoft doesn't mention .NET doesn't mean it's dead. They didn't mention C++ either, or MVC, or WCF, or Visual Studio. Nor did they mention installers, file compression or hedgehogs. Why does that mean they'll be nuked? And - and this is the big question - why are we getting hot and bothered by a Linux / mono guy spreading FUD??.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
Apparently, Chris, you've not kept yourself up to date on the current state of .net developer / Microsoft relations. This is not coming from a Linux guy, this is coming from a lot of recent negative history between Microsoft and Silverlight / WPF developers. You would be well served to get up to speed on it, it's a giant issue (apparently outside of these hallowed halls).
There is no failure only feedback
-
Apparently, Chris, you've not kept yourself up to date on the current state of .net developer / Microsoft relations. This is not coming from a Linux guy, this is coming from a lot of recent negative history between Microsoft and Silverlight / WPF developers. You would be well served to get up to speed on it, it's a giant issue (apparently outside of these hallowed halls).
There is no failure only feedback
You're right - I haven't been keeping up with the WPF/Silverlight community vs Microsoft, but that articles is written by a journalist whose bio says "Brian Proffitt is a veteran Linux and open source journalist/analyst with experience in a variety of technologies, including cloud, virtualization, and consumer devices." My main objection is that he says "there was little to no mention of .NET technology in the Windows 8 hoopla" as an argument to say ".NET is not part of Windows 8", and also to say there's a lot of anger [over the alleged omission of .NET / The plan to force Win8 apps to be HTML5] based on comments by readers who saw a UI/UX video that had no solid information on what the plans actually are. The overall issue is that Microsoft's messaging is awful. I think we can agree on that.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
-
You're right - I haven't been keeping up with the WPF/Silverlight community vs Microsoft, but that articles is written by a journalist whose bio says "Brian Proffitt is a veteran Linux and open source journalist/analyst with experience in a variety of technologies, including cloud, virtualization, and consumer devices." My main objection is that he says "there was little to no mention of .NET technology in the Windows 8 hoopla" as an argument to say ".NET is not part of Windows 8", and also to say there's a lot of anger [over the alleged omission of .NET / The plan to force Win8 apps to be HTML5] based on comments by readers who saw a UI/UX video that had no solid information on what the plans actually are. The overall issue is that Microsoft's messaging is awful. I think we can agree on that.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
He's just a symptom not the source which originally *appeared* to be Microsoft's horrible messaging, but when it happens so repeatedly and with such consistency at some point we have to stop being stupid as professionals and start reading between the lines. I think Microsoft is clearly cutting back drastically in their support for WPF / Silverlight / .net, all the signs are there, it's time for any business person to take a serious look at their commitment to Microsoft only technology going forward. After all Microsoft is basically *telling* us to do that, repeatedly and with zest, we'd be crazy not to take their advice. The days when Microsoft cared about developers, particularly small developers is long gone. They are taking us for granted and acting like other once great software companies who ended up being taken over by accountants and lost their heart and soul. Borland provides an excellent example, they were the standard for developer tools once. Microsoft is rapidly becoming the new Borland only they are bigger so they are taking longer to kill their developer market.
There is no failure only feedback
-
Did you miss the sarcasm ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
Did you miss the sarcasm ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
He's just a symptom not the source which originally *appeared* to be Microsoft's horrible messaging, but when it happens so repeatedly and with such consistency at some point we have to stop being stupid as professionals and start reading between the lines. I think Microsoft is clearly cutting back drastically in their support for WPF / Silverlight / .net, all the signs are there, it's time for any business person to take a serious look at their commitment to Microsoft only technology going forward. After all Microsoft is basically *telling* us to do that, repeatedly and with zest, we'd be crazy not to take their advice. The days when Microsoft cared about developers, particularly small developers is long gone. They are taking us for granted and acting like other once great software companies who ended up being taken over by accountants and lost their heart and soul. Borland provides an excellent example, they were the standard for developer tools once. Microsoft is rapidly becoming the new Borland only they are bigger so they are taking longer to kill their developer market.
There is no failure only feedback
I'm not sure I would extrapolate the uncertainties around WPF/Silverlight to .NET in general. From where I sit I see support for .NET continuing strongly. VS 2012, MVC3, Razor and the entity frameworks, the work on WCF and then all the work being put into dynamic extensions for the CLR and parallelism. Beyond that, integration of the developer tooling into the entire Microsoft application infrastructure such as Office speaks of a plan to entrench .NET even deeper rather than rollback.
cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP
