WPF old, still can rice no--say then said the future of WPF This Life (middle): strategy

?? In this article, "WPF is old enough to be able to eat"-say then said that the future of WPF: "Worry" continues. Some of the highlights in the "previous article":

Although WPF is no longer updated, WPF-based technologies are still evolving, such as the current WINRT, except that the API has a different set, XAML or XAML, data binding or data binding, dependency properties or dependency properties, templates or templates. In fact, I learned that the winrt of WPF is still relatively cool, the operation of blend has not changed, but now WINRT talent demand is indeed a bit pit.
Finally, we thank WPF for bringing us the development approach and development model of MVVM. by @h82258652

Although Winfrom itself to stop updating, but the tool has been upgrading AH! For example, vs Designer, C # syntax, third-party controls and open source components, and so on.
In addition, WinForm based on the Win32 API design itself is very mature, from the content is basically all-encompassing, Microsoft does not update will not have problems. by @winkingzhang

Technology is always to be replaced, some people say change an API to make money, but also funny, mapping out a lot of people to change the API will not be developed. I think, people update to update, we developers do in fact always one thing, write our code, do a good product.                 NET code is always written like that, right. by @ dried

Microsoft's new??? Strategy

?? In February 2014, Microsoft appointed a new CEO, Satia Nadra, from Microsoft's cloud services division.
He will take over as one of the reasons why the Stephen Bolmer, who does not understand the mobile market (first of all, the iphone and Android), may even be the cause of the market struggle between Microsoft and rivals (Apple and Samsung).

Contrary to his predecessor, Sati's global goal for Microsoft is "cloud first, mobile first", so it's a sensible strategy to jump out of the classic desktop market. But, to be exact, WPF is a design from an "old" model: This is a typical rich desktop application, and the relative WINRT uses a completely different design model that is closer to the needs of the mobile platform.
Of course, the desktop and stand-alone markets did not die, but apparently no longer alone burden.

Microsoft Business Store

??? To get the annual revenue of some application developers, many platform vendors such as Apple and Microsoft have created their own "stores", all of which are posted and purchased. As far as I know, unfortunately, Microsoft Store applications must be WINRT-based, so WPF-developed applications cannot be published to this store.
It is not a problem to note that some business-related applications are internally used and deployed, or that large application developers, such as ERP systems, have their own distribution channels, so this is not an issue; but for a small developer, it's a problem. Because you want to use the transparency of the market to ensure that before other competitors to seize the market.
More and more people instinctively choose to use the search function of the online store without knowing where to get a new application. If you develop a WPF application, you will find it difficult to release the product, not to mention the sale, so use WINRT to develop it.

Mobile sex??

If you get data every day from a browser on your mobile device or on a local app, you know the trends in the market today: your app needs a mobile version!
WPF is not a protagonist for mobile development at all, not even a supporting role, a few years ago, for Windows Phone customized Silverlight once unveiled, as the then Windows Phone 7 development tools. But a platform suite of development kits is obviously not a good idea, although you can share some procedures and tag code.
WinRT was born to this issue because it is a common toolset that is designed for the full range of Windows 8+ and is easy to develop, with a consistent system-level view. Some of these third-party controls support WinRT, such as:componentone Studio for WinRT XAML.

Maintenance??? Cost

? If you've been working on the Microsoft technology Platform all these years, you know that Microsoft is cautious about spending money, a good reason is, first of all, as a company to make money, but also more than the shareholders demand, so, can save it; second, many seemingly small small functions actually have a lot of work to do, Eric Lippert A lively description of his blog: How many Microsoft employees does it took to change a lightbulb??
Therefore, when the community mentions a bug or a new feature to fix, it will only be accepted if it is a big problem like the following two:
-critical issues, such as security breaches, even if few people encounter
-Small changes but countless people complain
Developing both WPF and WINRT will imply that two sets of functional requirements can be handled simultaneously, while repairing two bugs is clearly unreasonable, especially as Microsoft cuts spending.

Portability

Think about what makes WPF "survive", like developing a client application as a portable technology, but unfortunately it doesn't.
There is already a portable version of the. NET (refers to the academy, including the CLI): Mono, which can run under Windows and also run on Linux, Unix, and Mac. [Note: This article does not mention Microsoft.] NET open source, portable latest news]
In addition, mono is not a play-only technology, it is actually working, personally, I have built apps on Ubuntu servers and on the Jenkins Integration service.
Mono supports most of the technologies of the. NET Framework, except that WPF is not supported; If I remember right, there was a project called "Olive" once tried, but no real start, because the workload is too large, especially the underlying presentation layer.
The only interface that Mono supports is WinForm, and ironically, because of portability, WinForm can live better than WPF.

? Silverlight syndrome

When I was a Silverlight developer, I found that technology was dying faster than I thought. As time goes back to 2008/2009, Rich Internet Applications (RIA) is a very loud gimmick, and Microsoft has launched its own framework, Silverlight, and made public appearances in a series of Microsoft events that followed, in the hope that the various business executives could use them in their IT systems. The following 2010, until the first quarter of 2011, we were developing Silverlight applications.
But at a technical meeting in the next place, Microsoft announced that it would stop pushing Silverlight and instead start promoting the HTML5 ecosystem (including CSS and JavaScript). But the official said Silverlight didn't change, and I was very skeptical about it, and then my team decided to stop Silverlight development and turn to focus on "classic" WPF development, incidentally, with some benefits (for example, Silverlight is not " Plug and Play, but first requires administrator privileges to install the Silverlight runtime environment.

Thankfully, most of the XAML and C # code (about 85%) is shared with WPF, so there's no loss of too much, and we're going to stop for too much confirmation.
Eventually it was the right decision, because by 2013 Microsoft officially announced that Silverlight was terminated, and many it-related people were surprised because they didn't receive any warning.
I think this kind of thing will not be rough on WPF, but I think in today's IT environment and context, you must be very disappointed, from the suspicion, and even completely distrust.

[Not to be continued]

In view of the fact that WPF is old enough to be able to eat--say then says the future of WPF (ON): Worry netizens commented on the special statement :

Spread Studio 8 and ComponentOne 2014v3, ActiveReports 9, released recently in January, still offer product upgrades and technical support for WPF, WinRT, SilverLight .

Complete Article series:

• WPF old, still can rice no--say then said the future of WPF This Life (ON): Fear
• WPF old, still can rice no--say then said the future of WPF This Life (middle): strategy
• WPF old, still can rice no--say then said the future of WPF This Life (bottom): Peace of mind [translate ...]

WPF old, still can rice no--say then said the future of WPF This Life (middle): strategy