http://pragmateek.com/is-wpf-dead-the-present-and-future-of-wpf/
Contents [hide]
As a WPF developer for years I was recently concerned by the new direction chosen by Microsoft on its client platforms with the rise of the brand new WinRT framework.
I was concerned for good reasons: I’ve suffered from the collateral damages of the Silverlight failure, and as the proverb says “once bitten, twice shy”.
Since 2009 I have put a huge personal and professional investment in WPF, using it to develop LOB applications in the financial industry, and now I’m even providing training on this topic.
So as a professional developer and trainer the future of WPF is critical for me so I’ve studied this issue more thoroughly.
In this article I’ll share my findings with you, in a completely
objective and transparent manner, and I hope you’ll provide your own
facts, so that the community can have a better vision of the future of
WPF.
In the last part of this article I provide some strategies for businesses and individual developers.
Some reasons to worry
First I’ll start by presenting the signs that are worrying me, and should worry you too if you are a WPF stakeholder.
WPF team’s blog is idleAs every Microsoft technical team the WPF development team owns a blog where the team’s members share their expertise on WPF with the community.
The last article of this blog is dated from may 2011 so more than 3 years ago, precisely when WinRT was starting to emerge as the next big thing.
An idle blog could mean a lot of things but
근거가... 블로그 포스트...? - return 0;
배우신다고 해서 막을 권리야 없습니다.
뭐 vb6도 안 망했다면 안 망했다고 볼 수도 있지. 아직도 되니까.
아니 아저씨 VS가 wpf 라니까 - return 0;
참고로 이 글은 2014년 껀데 WinRT도 망했다.
WPF는 윈도우 스토어에서 안되지 않나?
wpf 책도 팔아야 되는데 왜 갖고 있는 걸까? 팔기도 귀찮다.
아는 사람 회사가 내부에서 막 싸워서 게임을 플래시 말고 실버라이트로 만들기로 했다던데 이제는 둘 다 망했네.