Today Microsoft Killed .NET Good-Bye WCF, WPF, WF, and Silverlight
I am afraid I am not as optimistic as some of the Microsoft gurus who make their money on Silverlight and WPF. Well not all of them. My Visual Studio Magazine just arrived and John Papa (Mr. Silverlight TV) has a nice article on JavaScript Tips. I guess we will soon be seeing JavaScript TV.(update 9/19/2011 - I guess not!! Good luck John, sounds like an awesome gig!!!)
I don't see the XAML tools in Windows 8 as first class citizens in Microsoft's development toolbox. Taking Blend and Visual Studio to HTML 5 and JavaScript land adds an acidy sour taste to my mouth.
I guess the WPF Disciples (http://wpfdisciples.wordpress.com/) will now be the Second Class XAML Disciples.
Mary-Jo sums it up well here.
After today's BUILD keynote I would switch to JAVA in a heartbeat if I could, but I have spent too much time in a Microsoft world.
I have not felt comfortable with Microsoft's leadership for a while now, and I don't see that changing anytime soon.
I am glad this happened when it did. I was about to embark on a new project. It was to have a WPF interface, a Silverlight interface, an MVC interface, and an ASP.NET interface. Different modules for different contexts. It will be time to rethink the choices.
My stance is, I don't need to pay $5000 a year for an MSDN to develop HTML, JavaScript, and CSS applications. I certainly don't need Microsoft to lead me down that path.
I cancelled several preordered .NET books today. One is shown below.
It is time to take a serious look at other options. Right now I am not willing to invest my time and money in the Microsoft future they presented today. Maybe after seeing more of BUILD I will change my mind, but for now my Microsoft technology learning track is put on hold.
I don't see the XAML tools in Windows 8 as first class citizens in Microsoft's development toolbox. Taking Blend and Visual Studio to HTML 5 and JavaScript land adds an acidy sour taste to my mouth.
I guess the WPF Disciples (http://wpfdisciples.wordpress.com/) will now be the Second Class XAML Disciples.
Mary-Jo sums it up well here.
After today's BUILD keynote I would switch to JAVA in a heartbeat if I could, but I have spent too much time in a Microsoft world.
I have not felt comfortable with Microsoft's leadership for a while now, and I don't see that changing anytime soon.
I am glad this happened when it did. I was about to embark on a new project. It was to have a WPF interface, a Silverlight interface, an MVC interface, and an ASP.NET interface. Different modules for different contexts. It will be time to rethink the choices.
My stance is, I don't need to pay $5000 a year for an MSDN to develop HTML, JavaScript, and CSS applications. I certainly don't need Microsoft to lead me down that path.
I cancelled several preordered .NET books today. One is shown below.
It is time to take a serious look at other options. Right now I am not willing to invest my time and money in the Microsoft future they presented today. Maybe after seeing more of BUILD I will change my mind, but for now my Microsoft technology learning track is put on hold.
 |
posted by tadanderson at 4:33 PM
4 Comments:
The Build conference sessions look evenly split between XAML/C#/C++ and HTML/CSS/JavaScript.
.NET is most certainly not dead. You cannot make a complete Win 8 Metro C# app without them -- look at the WinRT API -- you will need to use .NET to do anything useful.
MS is playing up HTML/JS in some strange attempt to attract open web developers to make Win native apps -- this will fail miserably.
XAML is much better for building UIs than HTML/CSS. Developers have a choice and no sane person will choose HTML over XAML.
I totally agree that Microsoft's messaging and developer communication is very bad right now.
@Art- Completely agree. SL is however dead. Let us say MS supports Silverlight for the next 10 years. That is great. But that means nothing to the customers I work with. Microsoft's poor communication over the past months built the coffin and BUILD put the nails in it when it was not even listed as a product. I lost a contract about 9 months or a year ago because of Bob M.'s comments, and rebooted a project because of BUILD.
I just restarted planning a major initiative that was to include a WPF interface, a Silverlight interface, an MVC interface, and an ASP.NET interface. It was luckily only a few weeks underway. Guess what NO ONE, including me, is willing to continue with Silverlight and WPF. They may not be dead @ MS as far as support goes, but MS killed them for us this week. Silverlight and WPF are no longer on my available technologies list for use until I see explicit Microsoft support, and not just the Silverlight evangelists request we accept implicit Microsoft support . I respect Jeremy Likness, John Papa, Pete Brown, Laurent Bugnion, but I can’t make recommendations based on their passion for a technology Microsoft is not supporting.
You should recycle yourself in humor!
Sorry that you're taking it so hard on yourself but quite frankly saying .NET is dead, and bye-bye to the technologies they've heavily invested into during the last 4 years is hilarious!
They are positioning a part of Windows to work well on the desktop, tablets and phones. They are creating a framework so that EVERYONE can write apps easily in the Metro UI. I just don't see what's wrong in merely adapting to the market reality and making it easy for Non-MS People to target METRO?
Unlike you, my glass is half full, not half empty. Instead of openly bitching on the internet like about 100k of you, I simply started to learn new stuff to complement my Silverlight practice so that I can actually write true multi-platform projects like Microsoft intends it to be done when my customers ask me to do so when Win8 gets released.
At the end of the day, it doesn't really matter that you are using legacy technologies to build stuff for you customers if that legacy tech gives you them an edge on their competitors.
@Francois
All good point, but a few days too late.
http://realworldsa.blogspot.com/2011/09/good-news-about-silverlight-and-wpf-for.html
The only issue I have is the fact that the legacy tech does not give them an edge over their competitors. Not even close.
Post a Comment
<< Home