News for hackers. Stuff that matters.
Re:Stick with Microsoft WPF (et al.) or jump ship? by teyc on Wednesday February 01, 2012 @05:30PM (#3540379)
From a developer's point of view there is nothing to do but just move on. From an organisational point, Microsoft has made it very expensive for people who wish to stay on the same stack.

The reason is MS needs to kill technologies in order for their new ones to gain critical mass. This has been done multiple times since VFP, VB6. The problem is no one has the money to redevelop the same app multiple times. Sometimes, developers are just fodder in the scheme of things.

Of course people will argue that the stacks themselves are still going to be around, but the ecosystem dies. No one produces new components for VB6 anymore. It used to be a thriving one. Another is the absence of performance fixes for WPF (search for Scott Barnes' (ex-MS Silverlight PM) rants on WPF). I've hit one with a Silverlight Grid which freezes with 1000 rows on MSIE due to assistive technology kicking in. These are never going to be addressed when a stack is put on ice.

Re:Stick with Microsoft WPF (et al.) or jump ship? by josephcooney on Wednesday February 01, 2012 @06:29PM (#3540633)
There are a bunch of new things for WPF in the .NET 4.5 release, including performance fixes.
Re:Stick with Microsoft WPF (et al.) or jump ship? by teyc on Wednesday February 01, 2012 @08:47PM (#3541058)
Yeah, I saw that. I was pleasantly surprised.