Here's something<http://visualstudiomagazine.com/articles/2014/02/11/satya-nadellas-to-do-list.aspx>from VS Magazine's website that might be of interest. The article arrogantly lays out a "laundry list" of things for the new CEO to look at. Unlikely he'll ever see this or take any notice of it, but it demonstrates the level of dissatisfaction that I and others are trying to articulate.
This paragraph is number 1 on the list. *1. Patch things up with developers. Let's be clear: killing Silverlight was hugely damaging to relations between developers and Microsoft. Today, Windows 8 development makes .NET developers feel less at-home than they once did, and side loading line-of-business apps is hard and expensive. Not only does Microsoft need to get its developer stack solidified, it needs more transparency around .NET, including an explicit roadmap going out several years. Killing Silverlight and deemphasizing WPF made developers very insecure. Microsoft need to take extraordinary confidence-building measures to make them feel safe and loyal again.* On 12 February 2014 21:21, Grant Maw <[email protected]> wrote: > Greg and Greg : +100 to your sentiments. > David Kean : does this answer your question? > > > On 12 February 2014 16:54, Greg Harris <[email protected]>wrote: > >> I do not think this was directed at me but here goes... >> >> >> Start rant >> >> >> @#$%^ing Microsoft has #$%^&ed me and the community on Silverlight, I >> spent a few years 100% focused on Silverlight at a significant cost in time >> and money, all now just wasted! >> >> >> Today, I have a client that would 100% fit a Silverlight solution for >> their line of business (LOB) application, but they are not willing to take >> on Silverlight because of Microsoft's end of life perspective on the tool. >> >> >> I would agree that it may not be the right cross platform tool for all >> mobile devices, but I see no reason why MS cannot make a commitment to >> future releases and ongoing support on Windows, Mac, Windows Phone and >> Android. >> >> >> I would not do the next version of Angry Birds with Silverlight, but I >> would do most LOB apps with Silverlight. >> >> >> Microsoft, you have made me angry, you have made my client's angry, you >> have lost credibility, I do not trust you! Probably more fool me for ever >> trusting you! >> >> >> Microsoft, you could start to gain some credibility back by restoring >> Silverlight to its rightful place as the tool of choice for client side >> development in LOB apps with a commitment to maintain and support it for 20 >> years into the future. >> >> >> End rant >> >> >> Regards >> >> Greg Harris >> >> >> On Wed, Feb 12, 2014 at 5:48 PM, Greg Keogh <[email protected]> wrote: >> >>> Greg? Where are you? >>>> This is your cue. >>>> >>> >>> Ah! What! I'm awake ... I saw Silverlight mentioned as dead and >>> abandoned. Guess what I've been doing all day today .. expanding a large >>> Silverlight 5 app. We have no alternative, we've spent years developing the >>> app and it's in use by some gigantic companies internationally. >>> >>> What the hell else can we do? Seriously! Discussion here last year >>> pointed out that HTML5 is the only alternative to delivering rich apps on >>> the browser desktop, but it groans under stress and I was warned that it >>> just can't show attractive interactive charts of the type available with >>> the ComponentOne SL libraries. >>> >>> Also, I have subscribed to MSDN Magazine (MSJ as it was) since 1993 and >>> I agree that it is generally uninteresting these days because it's mostly >>> about JavaScript, Stores, Azure, Windows RT and Windows 8 (the latest >>> groovy stuff you're talking about). I find I flip through new issues and >>> chuck them aside. I like academic articles, but Petzold's and McCaffrey's >>> articles are so abstract they're in the twilight zone. >>> >>> My day to day development experience is consistently as infuriating and >>> unpredictable as ever. Projects won't build, IIS goes haywire with code >>> 500s, versions clash, dependencies are all over the shop, kits don't work, >>> samples are simplistic, designers crash, I'm coding XAML UIs by hand, I >>> have to learn WiX, I have to run VS2013 and VS2012 side by side due to COM >>> problems, my VS2013 is diseased, and so on. I get up in the morning and the >>> things that worked the night before are all on the fritz. Sometimes I miss >>> punch cards. >>> >>> However, I don't want to fuel the jovial atmosphere of impending doom >>> that pervades this forum ;-) >>> >>> Greg >>> >> >> >
