For Your Review: We Are Under Review!
Wat Is It?
Yesterday at around 3:30 PM PT/ 6:30 PM ET, the Visual Studio team marked the premiere idea that this site was built around, Create a Ubiquitous .NET Client Application Development Model, as “Under Review.”
Wat Does That Mean?
Good question. It was marked without explanation, so it could be a mistake, or maybe someone pressed the wrong button somewhere. Additionally, another vote which I consider this vote’s “sibling vote” Bring Windows 10 Universal Apps to Android and iOS remains unmarked, so that only adds to the mystery. That might because that the sibling vote is really a Windows Platform concern or perhaps they will be updating it at a later time today or soon thereafter? Short answer here: your guess is as good as mine.
It is also possible that appearances do not deceive and this vote has indeed been uniquely marked as an issue worthy of review for the highly esteemed and legendary Visual Studio team.
Good question. The best analogy I can think of is that a mega party cruise liner in which an aspiring, brilliant business tycoon was running its technology enterprise out of (we’ll call it the S.S. Silverlight) somehow found its way into a terrible storm (we’ll call it Hurricane Sinofsky), where it was convincingly demolished, casting its seafaring, adventurous developers adrift, where they have either since died (moved to NodeJS) or they have found their way onto deserted islands (hanging on for dear life — and hope). On one of those islands, a determined, loyal (and maybe a little crazy) developer has somehow managed to send a flare into the sky, where a passing, hardened warship (the U.S.S. Visual Studio) might have seen something worth checking out.
OK, that wasn’t my analogy, it was Wilson’s. Wilson has great stories, don’t you, Wilson. Wilson is my friend. Wilson, tell me about the time when we could run .NET in a browser and on a Mac again, Wilson… Wilson, I love you, Wilson… WIIIILLLLLLLLLLLSOOOOOOOONNNNNNNNNNN!!!!!
Ahem, now where was I? Oh yes. Now obviously, if things are as they seem and this vote is indeed under review by the best team in Microsoft, then I am more than excited about it, even if it ends up going nowhere else. And I am not lost on this possibility. Consider the following items that are also “Under Review” on Visual Studio’s UserVoice, have over 1,000 votes, and have been left for dead by the Visual Studio team. To clarify, in my view (or from a project management perspective), “left for dead” means anything without a check-in or administrator message for over 6 months.
Here are those items, ordered from oldest to most “current” (for lack of a better word):
- Improve WPF Editor performance (Since September 18, 2011 — !!! Someone take this thing out to pasture!): 1,283 Votes
- Make Solutions Load Faster (Since June 14, 2013) : 1319 Votes
- Only load the components needed for the current scenario (Since June 14, 2013): 1,773 Votes
- Allow .NET games on Xbox One (Since April 24, 2014): 16,141 Votes (YIKES!)
- (FWIW, I have debated whether it should be included in the Weekly Vote Reports as a truly ubiquitous — and ultimate — .NET client presentation model would allow for games, too)
- Support for online/offline database sync for field devices without internet access (Since July 01, 2014): 1,099 Votes
- Improve the XAML Designer performance (Since December 17, 2014): 1,237 Votes
- XAML Debugging (Since January 23, 2015) – 1813 Votes
- VS IDE should support file patterns in project files (Since March 04, 2015): 3,431 Votes
- Support web.config style Transforms on any file in any project type (Since July 30, 2015): 7630 Votes
As you can see, there is reason to feel that this new found status change really doesn’t really mean much at all.
However, this vote does have a differentiating factor that separates it from the nine above, and that is the growing existential threat facing .NET that even is being perpetuated by Microsoft leadership in their baffling endorsement of NodeJS. Developers and organizations are quickly understanding that they can develop cheaper, more efficient solutions by ditching .NET and using NodeJS. Hopefully some key leadership positions in Microsoft (that care and understand about Microsoft investments and IP) are starting to see the error in their ways by backing NodeJS and realize that something must be done to stem the tide.
Show Your Support
We’re not out of the woods yet. The island is bare and food is scarce. Pick any other analogy you wish, the point is we are not done here, dear developers. If you are a .NET developer also feels left alone on a deserted island, please send a flare to Microsoft and the prestigious Visual Studio Team by continuing to support and show interest in a ubiquitous .NET client application development model offering. Furthermore, if you would like to read more about this idea, please see the series that I wrote on this idea here.
Thank you all for your past and continued support! It truly means the world to me.