Adolf Vs Windows 8 (semi-OT for entertainment purposes)
Posted: Mon Oct 15, 2012 2:13 am
I'm sure that we've all seen an absurd number of YouTube videos which sub-title the "Hitler Rant" scene in the movie Downfall. Most of them are just a series of non sequiturs which don't even remotely tie to the video content, and which the creator stuck over the top hoping that the fame (infamy?) of the clip would disguise the lack of coherent content.
But every so often you come across one where the creator has put in some effort to nail a topic. In this case, Microsoft's ambivalence to the continued development of Silverlight and WPF applications under .Net in Windows 8 and onwards. (The poster of the video is no relation, distant or otherwise.)
If you're on the periphery of Windows development without any strong commitment to a code base but are generally familiar with the WPF/Silverlight vs HTML 5 issue (including the (in)famous "strategy has shifted" comment that {cough} approximately coincided with the departure of Bob Muglia from MSFT), you may find this parody, as I did, laugh out loud material.
If, on the other hand, you've buried yourself in WPF in an attempt to become a Zen master of it for the last couple of years, you're more likely to kick your screen.
For mine, I saw some things in WPF that made me think "hmm, cool, I'd like my app to be able to do that". But, given the way that MS has screwed us over on a number of things in the past (VB6 (which was essentially abandoned, since VB.Net is NOT VB7 onwards), a new data object model every couple of weeks, user level security in Access (which really doesn't matter I suppose since SQL Server makes Access a waste of space IMHO) etc, etc) I wanted to be sure that I wasn't wasting my time especially as I didn't find WPF all that intuitive to work with compared to Windows Forms. But, of course, part of that comes back to me not having put in the time to learn it as well as being rather less enthusiastic than most of the planet about XML and any distant family relatives thereof.
From what I've read I suspect that I would have been wasting my time, so while WinForms won't do everything I'd like they'll do everything that I need, and given the uncertain future of WPF I think that's what I'll stick with.
But with MS being seemingly unable to commit to a technology I must confess that I almost... almost... understand Iboglix doing sod all to develop the .Net API for TM1. (Some of the wilder speculation has tied the downfall of Silverlight / WPF to an eventual downfall of the .Net framework... but if that happens, it's the end of MSFT IMHO. I can't see it in the foreseeable future.)
But every so often you come across one where the creator has put in some effort to nail a topic. In this case, Microsoft's ambivalence to the continued development of Silverlight and WPF applications under .Net in Windows 8 and onwards. (The poster of the video is no relation, distant or otherwise.)
If you're on the periphery of Windows development without any strong commitment to a code base but are generally familiar with the WPF/Silverlight vs HTML 5 issue (including the (in)famous "strategy has shifted" comment that {cough} approximately coincided with the departure of Bob Muglia from MSFT), you may find this parody, as I did, laugh out loud material.
If, on the other hand, you've buried yourself in WPF in an attempt to become a Zen master of it for the last couple of years, you're more likely to kick your screen.
For mine, I saw some things in WPF that made me think "hmm, cool, I'd like my app to be able to do that". But, given the way that MS has screwed us over on a number of things in the past (VB6 (which was essentially abandoned, since VB.Net is NOT VB7 onwards), a new data object model every couple of weeks, user level security in Access (which really doesn't matter I suppose since SQL Server makes Access a waste of space IMHO) etc, etc) I wanted to be sure that I wasn't wasting my time especially as I didn't find WPF all that intuitive to work with compared to Windows Forms. But, of course, part of that comes back to me not having put in the time to learn it as well as being rather less enthusiastic than most of the planet about XML and any distant family relatives thereof.
From what I've read I suspect that I would have been wasting my time, so while WinForms won't do everything I'd like they'll do everything that I need, and given the uncertain future of WPF I think that's what I'll stick with.
But with MS being seemingly unable to commit to a technology I must confess that I almost... almost... understand Iboglix doing sod all to develop the .Net API for TM1. (Some of the wilder speculation has tied the downfall of Silverlight / WPF to an eventual downfall of the .Net framework... but if that happens, it's the end of MSFT IMHO. I can't see it in the foreseeable future.)