41–50 of 99 posts
This article is dead on from my perspective. I was one of those long-time Windows devs, started on the Win16 API, and I had invested quite a bit of time and effort into WPF and Silverlight because I thought it was cool. I remember that exact announcement, and my immediate thought was that they were ditching WPF/XAML for this new thing, whatever it was, and I just could not see where that was going. I started working…
Some people will complain that windows tries too hard to maintain backward compatibility and others will complain when they don't. Its like damned if you do or damned if you don't.
I mistakenly stuck with .Net and ended up going to back end data work before returning to the web side as I had begun years before. Things are good on the web and cloud side but I stick see Xaml as too risky to go back to now, even with Xamarin.
I remember it all too well. I was a WPF contractor in early 2011 and Silverlight was the one of the best paying skills so it was the thing to learn until the confusion of that announcement. I got a short Silverlight role at the end of 2011 but after that things dried up totally just as I was hoping to buy a home when they were affordable. I mistakenly stuck with .Net and ended up going to back end data work before re…
It's crazy to think that the owner of the win32 API, probably the strongest asset in contemporary computing, ended up with such a disorganized developer story - winforms, wpf, winrt, silverlight, html. The last thing you want your "developers, developers, developers" to do is to stop and think about which APIs they need to evaluate switching to. Because that's how you build mindshare on iOS, Android, OSX, ChromeOS.
It's WinRT via .net/C++/js for future apps. Everything else is legacy supported.
Earlier quoted context omitted.
According to the chart on that site, Windows 7 is still at 44%. That very much sounds like "not being able to overcome past Windows versions in market share" to me.
Nope. Look at the graphs for Windows 7 and Windows 10(assuming that's the dotted line) over the whole recorded time starting in 2008. Windows 10 is roughly following Windows 7's trajectory, if not exceeding it a little bit. It took Windows 7 over two years to initially reach 44%. Windows 10 has been out for only about a year now.
It's crazy to think that the owner of the win32 API, probably the strongest asset in contemporary computing, ended up with such a disorganized developer story - winforms, wpf, winrt, silverlight, html. The last thing you want your "developers, developers, developers" to do is to stop and think about which APIs they need to evaluate switching to. Because that's how you build mindshare on iOS, Android, OSX, ChromeOS.
It's WinRT via .net/C++/js for future apps. Everything else is legacy supported.
I don't agree. Switched my main focus to .NET around 4 years ago, and we keep on having more requests for proposals than we can fulfil, including new applications.
I totally agree the mishandling on the Windows 8 announcement is what killed windows just as it was getting good. The freedom to style WPF apps would have made Windows keep it's place as the OS that you could make your own but Windows 10 is trying to be Apple, constraining what you can and can't do and forcing you through an App Store.
And here I am still stuck on WinForms grids. WPF is too slow and the JS frameworks just spin endlessly when I try to throw the amount of data I need to display at them.
Earlier quoted context omitted.
It's WinRT via .net/C++/js for future apps. Everything else is legacy supported.
Is anybody actually building Universal apps, though? I just don't see any of the desktop apps with massive existing code bases jumping ship anytime soon, if ever.