Earlier quoted context omitted.
It's WinRT via .net/C++/js for future apps. Everything else is legacy supported.
And what if I need to continue to support users who are running Windows 7?
Doesn't mean it's not legacy
How one announcement damaged the .NET ecosystem on Windows
71–80 of 99 posts
Re: How one announcement damaged the .NET ecosystem on Windows
#72Microsoft is just that good in "Orborning" themselves. (also "Ratnering" too, and saw some people here in HN creating the name "Elop effect" that is when you do a "Osborne" and a "Ratner" in the same announcement). Some examples: 1. That Memo "Symbian is dead", when in the third world Symbian was crushing the iPhone like a hydraulic press, due to its sheer utility/price performance (ie: being almost useful was the iP…
The old DirectX redists are dead and has been since Vista. I think they relied on the old XP display driver model. Only time they did it since was Platform Update for Windows Vista.
Re: How one announcement damaged the .NET ecosystem on Windows
#73This 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…
WPF and WinRT share similar ways of working.
You could say that about most Microsoft APIs/platforms over the years. The key difference for me is that when it was Win16 -> Win32 and then COM/DCOM -> MFC -> ATL -> .NET -> etc. there weren't really many viable alternatives to deliver software to a large user base. That has all changed dramatically, and so it was important for MS to be very clear, and they weren't. Of course there are other factors as well: it used to be cheap to be an MS dev and then it got very expensive and is now back to cheap-ish again; they used to be the jeans and a t-shirt insurgent and now they're the big enterprise IT vendor, etc., etc.
Re: How one announcement damaged the .NET ecosystem on Windows
#74The Windows Store is still a wasteland, and we're four or five years on at this point. The Windows 8 tablet-ification push was a serious misstep, and it is a damned shame, because the underlying guts of Windows have gotten much better since Win7.
I remember that many of this stuff was in the old developer preview from 2011. While at it, I should also mention the update that was originally planned for Win8.1 to bring start menu back.
Re: How one announcement damaged the .NET ecosystem on Windows
#75The most annoying thing about Sinofsky is that nowadays he's all in on anything Apple related. That makes one wonder why he made such disastrous decisions when he was in charge of Windows.
Apple execs were publicly (and rightfully) mocking the Windows 8/RT mess he created and today he's unironically critical of its aftermath while praising Apples stellar execution.
Re: How one announcement damaged the .NET ecosystem on Windows
#76Bob Muglia did something similar with Silverlight back in 2010. As I'd invested two years of my life into a Silverlight-based startup at that point, it effectively killed two years' worth of work, and left me rather soured on Microsoft. http://blog.wouldbetheologian.com/2010/11/its-about-trust-mu...
> Silverlight-based startup Even without hindsight, it seems short sighted to have bet on Silverlight.
I startup a Windows Store Analytics based startup - sometimes you take a bet on a technology taking off and it doesn't work out. Look at how many people ate shit building startups on top of Facebook's platforms over the years. Don't judge us too harshly ;)
Re: How one announcement damaged the .NET ecosystem on Windows
#77It's not just one announcement; they keep changing their mind about what the future of the windows API is. WinRT is the final nail in the coffin. Now with WinRT on one side being tied to Windows Store apps and .net/WPF on the other side being limited to normal desktop applications, who in their right mind would devote time to building an app in either? In particular, if you're making enterprise software, for example,…
.NET runs on both, just not 100% API compatible. Mac OS X and iOS aren't also 100% compatible, neither are ChromeOS and Android.
I consider that as an attack on General Purpose Computation by the likes of Apple and Google.
Re: How one announcement damaged the .NET ecosystem on Windows
#78Microsoft is just that good in "Orborning" themselves. (also "Ratnering" too, and saw some people here in HN creating the name "Elop effect" that is when you do a "Osborne" and a "Ratner" in the same announcement). Some examples: 1. That Memo "Symbian is dead", when in the third world Symbian was crushing the iPhone like a hydraulic press, due to its sheer utility/price performance (ie: being almost useful was the iP…
[deleted]
Re: How one announcement damaged the .NET ecosystem on Windows
#79Microsoft is just that good in "Orborning" themselves. (also "Ratnering" too, and saw some people here in HN creating the name "Elop effect" that is when you do a "Osborne" and a "Ratner" in the same announcement). Some examples: 1. That Memo "Symbian is dead", when in the third world Symbian was crushing the iPhone like a hydraulic press, due to its sheer utility/price performance (ie: being almost useful was the iP…
In PC gaming, Windows 10 is 38% now. It's more than Windows 7. PC gamers prefer Windows 10 because of DX12. See in Steam.
http://store.steampowered.com/hwsurvey
Re: How one announcement damaged the .NET ecosystem on Windows
#80It's not just one announcement; they keep changing their mind about what the future of the windows API is. WinRT is the final nail in the coffin. Now with WinRT on one side being tied to Windows Store apps and .net/WPF on the other side being limited to normal desktop applications, who in their right mind would devote time to building an app in either? In particular, if you're making enterprise software, for example,…
I am also burnt out on them. Winforms, Silverlight, WPF, WinRT now UWP. Just wait for the next change of mind. We have gone web even for internal stuff that would have been web based before.
If I absolutely needed a desktop app I would either go Qt or write my own simple win32 wrapper.