I have noticed in a few places discussions comparing the UI and API of WinRT with Silverlight, and suggesting that it (WinRT) is preferable. Mostly, these were quite old posts (a series of 6 or more at SharpGIS was my first sense of this).
It does raise the possibility that Windows / Microsoft will rebirth or rethink some technologies.
Related (in my eyes, anyway), apparently there is a wider discussion about Windows 9 (based on leaks and conjecture) suggesting that there is to be a complete rethink of Windows market segments in Windows 9 “Threshold”.
It’s summarised here in InfoWorld (December 2013) in an article by some bloke named Woody Leonhard.
He sets the tone in his first sentence:
“If independent leaks are to be believed, Windows chief Terry Myerson appears to be dismantling the Jekyll-and-Hyde monstrosity that is Windows 8, instead replacing it with a triumvirate of products that people and companies will actually want.”
I’ll be interested in Scott’s comments on the triumverate of products, including the quote that refers to Terry Myerson’s supposed intentions.My thoughts/Reply I don't know much about the future of Microsoft because I suspect not many INSIDE Microsoft themselves have a clear definitive handle on that (not to sound jaded, i honestly do believe they are still haggling over how to raise the broken into fixable solutions). I would say this, the company has built up enough equity in the past to make a full focused run at Consumer adoption for products that would typically sell reasonably if not better in enterprise/smallbiz but they in the end hit a wall. I think it was mainly they didn't understand the consumers needs and were to busy trying to graph compete strategies they have used on Enterprise into the same space as consumers (Internally Microsoft can be quite aggressive and paralysed with fear around competitive events - its a huge weakness imho). If you were to unpack Windows 8 today and really take a step back from it all, there's not a lot of negativity associated with what they have done. I look at Windows 8 as the parity release between Silverlight/WPF and all the fixes customers (devs) wanted but it was delivered in a way that traumatised the base. It could have been delivered with a softer approach to change management in that instead of holding a gun to our collective heads with the intent of "upgrade or else" simple things like namespace / sdk related issues would have been enough to build confidence with the developer base around migration / roadmap. A developer would be fine with with Windows 7 WPF/Silverlight development today provided they know eventually with a Windows 8 upgrade the performance and scaleability issues would naturally resolve themselves (ie devs dont spend to much time haggling over the rendering pipeline). If you then combine Windows Phone 8 (which is really still in many ways the Silverlight behaviour) you again then tick the other box around reach on mobility devices. You are still locking them down into a world called "windows" which doesn't piss a lot of enterprise companies off, especially with the current turbulence in the device market we see today. Enterprise companies right now are a little paranoid or scared about their mobility adoption strategies because its one thing to say "I want breadth" and another to say "i want breadth and depth' when it comes to User experiences that count. If a company wants to get their "mobility" story together, they often associate mobility with web because breadth is far more attractive story than a depth discussion. Breadth means HTML/JS because it means I don't have to have specialist teams (Java, ObjectiveC, C#/Mono etc). Depth requires the opposite because you can only put off that problem for so long before someone within a team suddenly comes to work wearing his/her "Java Conference 1998" t-shirt and smells funny because they do Android development. Microsoft had an opportunity to do a simple rinse/repeat on the "Embrace/Extend" model with Windows and like I said, Enterprise would likely have been fine to play in that sandpit (of course they'd keep pushing on the "make my C#/XAML apps work on all" angle every step of the way). In keeping Enterprise bellies full that would have stabilised at the very least their largest piece of the profit share pie, in that they would have bought themselves another 2-5 years to focus on Consumer more without having to pay the tax on losing hearts/minds of business grade solutions. This would have also given them more adoption metrics around the mobility + desktop upgrade story because if a company buys 10-100 units of one piece of hardware because it was easier to develop against well thats 10-100 forced adoption(s) on users which after a while could turn into positive/negative evangelist for those products (Forced adoption is not a bad strategy ...its just ethically horrid). But.. sadly none of the above has happened, instead Sinofsky wen't rogue, went aggressive not just internally but externally and let his own self-inflated arrogance steer the ship in a direction of aggressive change management which has backfired. Now the new heads of state have to figure out how to salvage what they have left into meaningful pieces that can essentially tap into the above behaviours. The article is right, you have really three options - fade out you core business (enterprise) and go full retard on consumers adoption, reverse the namespace/SDK engines and build a bridge between old and new but lose what small foothold you have on consumers - or - abandon consumer focus and retreat back to safety around enterprise/small business. I'd place my money on the 2nd option, bridge building but that's going to be filled with a lot of apologies and the only way they can even attempt to make that work is to ramp up their DPE practices beyond where it is today (that is a lot of people on a lot of planes, apologising and seeding a new/existing audience with solutions). The head of DPE (former CEO of Skype) is a business development numbers guy who clearly has no real passion for DPE, so i don't see how even if they find a way to build that bridge can make that happen (it's an attitude issue as well as a technical one). Building a bridge between old and new is not as scary as one would assume (well i don't anyway), there is a lot of positive work put into the Windows 8 SDK's .. i don't think anyone can say out-loud that Microsoft doesn't get their shit together technically when given the chance, there is and has always been more positives in their technical abilities than negatives - it just always always always comes down to the way in which they deliver the message and react to developer/customer issues of the day. Is it really a case of just refactoring Windows 8 namepsaces or proxy classes of some sort to convince Developers to continue on WPF/Silverlight path? ... Is it a matter of just investing more in that "devigner" tooling problem (Expression Blend makes a comeback but with less reliance of "reflection" based property grids). *shrug* .. i can personally see a way they could rebuild and get on with the Windows 9 approach and I don't think it requires a radical overhaul but more architectural common sense.
Question. If we all say WPF, is dead, wont that hurt its present day adoption?Answer. Yes. Definitely and I have personally been at the bruising end of that conversation. There is no doubt that if we the .NET community declare WPF end of life we in turn let Microsoft get away with their bad decision making (in truth my bad decision making as its former Product Manager) and lastly we shoot ourselves in the foot for future XAML friendly work. Having said that, declaring it dead is important short-term loss but potentially long term gain and I will explain why. Mobility platform adoption is at critical crossroads. Today companies worldwide are under a lot of pressure to discuss what their software offerings in and around web + mobility are likely to be. That is to say, the sales pipelines are handing feedback up stream that ask the question in around “when are we going to be mobile” (not in a literal sense but conceptually). If we today continue to prop up WPF as a “good enough” technology bet knowing Microsoft has abandoned any further support then we are placing the entire .NET community at risk of alternative development. This is to say that most developers who are bored with .NET or do not’ care will not be fussed either way and probably would embrace this all the more. Developers who do enjoy sitting inside Visual Studio and dare I say, Expression Blend might find this a troublesome thought to contemplate. The fact of the matter is .NET development is successful given its tooling story and .NET framework often gets you in and out of the development workload quite fast (I am a former Java/ActionScript developer, so I am not saying this a pure .NET whore). If we ignore the Windows 8 and Windows Phone 8 proposition in favor of high fiving WPF, well we are placing our short-term bets on desktop development here and now whilst leaving the whole mobility continuance exposed to iOS or Android development. This in turn can have a knock on effect, whereby developers in the .NET space are given a choice of either doubling down on HTML5, up/down-skilling in iOS or Android development practices or worse being outsourced to specialist teams who have prior experience in the alternative(s). WPF has no mobility story other than a remote desktop application on an iPad touching a desktop built in WPF (messy and clumsy). I see the whole Windows 8 proposition as a mess; do not get me wrong Microsoft have done us all no favors with their UI choice(s), developer relations nightmare and lastly internal bickering and constant wave after wave of aggressive behavior. It is time the company either started to fire some executives or regroup and come up with a better strategy than the one(s) they have now. Until such time, it in the end it has been left up to Architects worldwide who have influence to provide clarity around what the Microsoft mobility offerings look like and help position new projects towards this in a calm manner. I am not saying this will happen overnight it will probably take 1-2 years to push the business community into the Microsoft Windows-only mobility space. If we also can carefully, correct Microsoft messaging that WPF is dead whilst at the same time Windows 8 is the next version of WPF (current source code, tooling and skill reuse), you stand a greater chance of success than you do by choosing to downplay its state. The trick is to go beyond Microsoft’s weak guidance today that “Silverlight & WPF aren’t dead, XAML/C# are alive!” as if that was the answer to the question. It clearly needs to be expanded on further and teased out in careful threads on what that actually means. It’s not about XAML/C# it’s about “can I keep my existing work on Windows 8” first and foremost. If they can answer that question with clear and definitive guidance the whole WPF is dead becomes less of a bad taste. If they cannot answer that, then look to the blogger left or right of you and pray they understand Microsoft better than they themselves as its coming down to the ye olde “influencer takes all” position. Ubiquity seems to always be a sticking point with Microsoft. The fact that WPF right now has probably one of the best ubiquity stories that would make Silverlight at its peak salivate with envy still goes largely unnoticed. It has to do with Microsoft’s lack of marketing & evangelism around this but in reality you could knock out a WPF application and reach more audiences than most other languages. Think about that, how many Windows machines are there worldwide, specifically when it comes to Business customers (less consumer). Now what has always been the sticking point about making applications in HTML vs. Windows? Answer – cross platform. Having cross-platform has always been most sort after request and the main core reason why WPF adoption has often been parked in the “maybe next time” bay. The amount of times at Microsoft when I was in the Product Management team we faced this issue we would often just retreat to Silverlight as an answer hoping that would get deals across the line where possible (hence Silverlight got all the investment and WPF didn’t). The reality is Microsoft is a Windows only company and for a while, Silverlight and its x-platform strategies distracted us all, but ultimately that is what killed it. Microsoft cannot as a company afford any more to be semi-agnostic; they are losing so much market share right now it is ridiculous. They now have to regroup (Windows 8 product lines) and go back to their tired playbook of “Windows Only or bus” (it’s the only trick Sinofsky knows). If Microsoft cannot position WPF as a viable solution to real problems and instead are bowled over with weak answers to the cross-platform perception then what are we all doing? Do you keep fighting the lonely fight or do you regroup and rally behind the one thing that actually might get you out of this discussion a bit more cleanly via the Windows 8 pitch. Tooling is tapering off. I do not see Visual Studio 2012+ and Blend+ continuing much more in investment around Windows 7 + WPF. We all saw this happen with WinForms and it is not as if they will cut and run with these two, they just will not spend too much time on the problems that are faced with tooling for WPF. WPF is likely to still have internal investment so long as Expression Blend and Visual Studio continue to pull from its code base how that spills over to the public though is an open question (that will not yield answers). It is in Microsoft best interest to turn a cold shoulder here on WPF (despite its internal adoption) publically in order to get everyone shifted over to Windows 8 in a more timely manner. If they let WPF linger or keep feeding it backwards compatibility then it turn becomes what Windows XP has been to Windows 7 or Internet Explorer 6 to Internet Explorer 9 … a legacy you just can’t kill off no matter how much you promise “new” is better.
Question. Ok, so you are saying let’s all announce WPF is dead and long live Windows 8?Answer. Yes. Before you grab your stones and start throwing my way, it comes back to the key driving principle behind why that is. Do you optimize for a short-term gain and in turn leave the mobility and future platform battle to the alternatives or do you instead promote its end of life but do one better than Microsoft themselves by outlining what the transition will look like over the next two years. What I mean to say is, do not just say, “its dead, end of story”. Instead, say, “It’s dead as long as Windows 7 isn’t alive. The future of WPF however is tied-up in Windows 8, so if we want to get more into mobility then we have a transition moment here. We can continue to keep existing code that we have written and transport it across primarily. Secondly, we can also retain our developers skill sets that we have invested today given the tooling and languages are still intact (with minor and major modifications throughout). It sux and I am facing the same issue right now. As I sit here and type this on my Office 13 Preview via my Windows 8 Install, I am doing so under duress. Do I like Windows 8? I don’t like the UI, sorry I think Metro is a form of mass design retardation in full flight but on the flipside I can live with it provided I get a UX platform that I can do more with. I will trade my dislike for Windows 8 upfront if it can let me create a vision of what I think the software industry should do with its out of date workflows & problem solving. I’ve waited 15 years+ for a descent UX platform to come along, I sat through VRML, DHTML, Flash, Flex, WPF, Silverlight and now this hell spawn known as Windows 8. I worked as an outsider and insider on all of the above and I’ll be damned if I’ll give up now because some bald headed napoleon complex ass-hat decides “He’s got Steve Jobs beat”.
Question. You are still putting developer’s jobs on the line.Answer. Yeah I probably am. I am not proud of that fact and when I was part of a team that funded Silverlight & WPF we actively choose to ignore WPF in favor of Silverlight. It was a calculated bet at the time but clearly, the result is we have two products facing a slow death march in favor of a reboot to a solution we almost had at the start. Let me unpick that further. When I first joined Microsoft, we were fighting to get WPF into the hands of .NET developers worldwide. We needed to move everyone from Windows XP over to Windows Vista and in a timely fashion. Microsoft spent millions pushing the agenda alongside getting Office Open XML blessed as a standard (given it would help influence adoption). The whole thing was a mess and as a result Silverlight was born if anything as a way to buy some time around what to do in terms of solving cross-browser and cross-platform related issues (with a keen eye on mobility). Silverlight did its job initially but in the end, the chaos that flowed from those days to today still is haunting us all. My point is that by talking openly about the technology platforms the way I have, I am looking to cut through the political and chaos that is before us today. I am looking to instead help others diagnose the problem aloud as in order to solve a problem you first have to admit you have one. WPF is dead. Ok. Now what. Do you go HTML5? Probably yes, but do you honestly think WPF being alive or dead have influence to this discussion – more to the point do you think this blog is going to send companies racing for HTML5 now? I would say if a decision is to go down the HTML5 path that thought was planted well before I arrived there. Do you invest in iOS or Android? Again, go for it watch the dollars you were going to spend on HTML5 and WPF escalate given its not only foreign development practices to your existing .NET space but you probably will have to absorb the time to up skill or hiring of specialist teams to do the work (India outsourcing can only buy you so much). If this blog is the catalyst to a WPF team getting the termination letters then you were cooked well before I arrived I’m just the 1000th cut.
Q. Is WPF Dead?A. Yes and No. Yes WPF as you see it before you is end of life that is to say no more code will be written for the “platform” given Windows 7 and Windows 8 have different DNA going forward. No as in when we decided to move everything over to leaner Windows 8 platform we had to put both Silverlight and WPF on a diet in order to get Mobility parity / compatibility in check. The Upside is we’ve fixed some of the UI rendering issues that have plagued you in the past; the down side is we’ve had to sacrifice features here and there in the process.
Q. If I make an Application today in WPF it won’t work in Windows 8 tomorrow.A. Not correct. Expression Blend uses WPF still in Windows 8, so in a way you’re covered as long as VS2012 and Blend continue to take their cue from the previous XAML Rendering that has been in place since Windows 7. There are certain things you can’t do in Windows 8 going forward though, that is to say new features won’t work in both Windows 7 and Windows 8 for obvious reasons. If they aren’t obvious then …stop coding now.
Q. Do I have to learn HTML5 or C++ in Windows 8 now?A. No. The neat trick here is that we took the body of work found in Silverlight and made it handle the rendering of XAML. Now we didn’t take it as-is we again had to scale it back and use it as a starting point for a reboot of WPF/Silverlight to ensure two things happen going forward. The first is that we have WPF/Silverlight parity issues resolved in terms of performance and developer centric API changes whilst at the same time we had to find a way to make Steve Sinofsky believe that Silverlight was killed off. The last point wasn’t a technical issue it was more of a political one and so in order to help give him the illusion of Silverlight’s death we renamed a few namespaces and adjusted a few features here and there to give the appearance of “new” on the “old”.
Q. Why did you change so much in Windows 8 to confuse us all on old vs. new?A. We had to find a way to put Internet Explorer back into the hands of the masses in a more aggressive manner. In order to facilitate this internal metric we needed to also scale back Silverlight’s popularity given when you think about its future roadmap and Internet Explorer the two will end up competing with one another. Having Internet Explorer start taking over the HTML5 discussion would also help us win hearts and minds with the non-.NET crowd which would then help boost our internal metrics around Linux, Php, Apache and MySQL/Oracle compete (that has often plagued us for many a fiscal year). Once we’ve placed Internet Explorer onto many devices worldwide we will then ask developers to fork their beloved HTML5 in a way that lets them access Windows 8 further. This in turn will help us regain the lost dominance we once had before all of our Internet Explorer staff left the company to work for Google Chrome. Additionally, it will help us with our many year attempts at attracting more developers to our Windows Server & Tooling business units. Now to answer your actual question it’s important to know the previous strategy for Internet Explorer as now the problem we face both internally and externally is how we are going to balance Internet Explorer’s future with XAML given the old “Silverlight” concept was directly competing with this strategy. In short we had to make it feel there was a lot of change in the room and decided that letting you believe that what’s really happened is that WPF & Silverlight were merged as one and that Silverlight 5 wasn’t the last release as really Windows 8 is Silverlight 6 Desktop. Letting you believe that would keep you preoccupied with that branch of thought where what we need you to do is come back to the Internet Explorer way of thinking – there is no plugin only a browser.
Q. So… you saying Windows 8 is really Silverlight 6?A. Yeah in concept yes. Technically no, but if you take a step back from our bad messaging, public relation screw-ups and lastly our idiotic executive we pretty much did what you asked – we fixed WPF and Silverlight parity & performance and we made it also work on both desktop and mobile. I give you Windows 8.
Q. Well ..why didn’t you just say that? Why did you scare us with C++ or HTML5 rhetoric?A. I have no answer suffice to say there was lots of infighting going on and I don’t see Soma and Sinofsky sharing a beer or two at a BBQ in the near future unless the bottle was broken and one has the other pinned down with a desire to kill..
Q. You said mobility and parity are you saying Windows 8 is compatible with Windows Phone?A. Yes. Windows Phone 7 was kind of a hold our place in the line while we figure out what to do next release. It was badly marketed and in the end we were too late to enter the market – not to mention we weren’t ready to talk about the work we were doing with Windows 8. Now that we’ve finally hit reset on Windows Phone via our 8.0 releases we’ve now found a way to put the XAML rendering we have in Windows 8 onto the phone. Well to be fair we really kept Silverlight’s DNA alive in both which has now let us enable you to write applications on both platforms via our new upgraded API’s and tooling (again to give the appearance of new). This is in part why you can’t use Windows Phone 8 code on Windows Phone 7.x compatible devices, Additionally you would see how we swapped the two out and start to guess what really happened during the Soma vs. Sinofsky fight.
Q. I don’t think that’s technically correct.. if you look at Windows Phone 7 and then look at…A. I’ma let you finish by stating that the phone may not have changed radically but Windows did that is to say if you were going to drag Silverlight’s work into the new Windows 8 whilst releasing Windows Phone 7 previously then which of the two do you change? The phone or operating system? – Answer is you do both but incrementally.
Q. Hang on so all of Windows 8 is now Silverlight? That doesn’t make sense..A. No. Windows 8 core is, (as the messaging and PowerPoint decks say,) new. Now the XAML piece that bolts on top of that core is what I’d call “Silverlight 6” that is it’s all the work that has been done on WPF/Silverlight since their birth converging as one.
Platform Adoption - Use Case.Garnter’s VP recently came out and stated that 80% of businesses by 2013 will be outfitting staff essentially with an iPad like device. It’s a pretty bold stat and you have to remember that Gartner get paid to come up with research by companies that need the said research to abstract their sales pitch from bised to unbiased opinion - that being said - it’s not unreasonable to believe what he stated. Picking up a mobile device like an iPad at first seems like it’s a toy, or unnessary for variety of industries as they will never replace a desktop device. An assumption like this will be short lived in most large companies that are weighing up their platform decision making. Firstly concept of an iPad in the hands of an after hours worker is more valuable than a laptop. The main reason is they are carrying the device around with them and are more likely to whip it out during a dinner with friends than a laptop or slate (excuse me while I take out my laptop, no continue talking vs let me look at this device that almost to the untrained eye gives you the appearance i’m checking the bill for our dinner folder thingy). The worker opens the device, performs some quick “at a glance” review of the data within their company, see’s no urgent issues and continues to go about their evening. Having First response reactions are highly valuable and will be the likely first candidate for mobility in most verticals. It’s more to do with the psychology of the device than its possibilities that is to say you could shift a lot of your desktop solutions onto an iPad-like experience but it won't’ happen until organisations wrap their heads around Security and how they plan to break up their current desktop experience(s) into more finite pieces. Security will be the biggest sticking point initially and UX Technology adoption aside, it comes back to the fear that if a user were to leave the said device at a dinner table then people can shut down a factory or steal intellectual property from a company faster than if they were on say a laptop (yes it's retarded but you know there’s a Security jackass in some IT Division scaring the kids with just that scenario and getting traction). A company will in turn dip their toes in the water, they’ll use Frist Response workflow / process as a way to see if this whole Mobile thing has legs from an investment standpoint and technical adoption acid test.
Platform Adoption - Windows 8 Hijack.Having forked browser discussions or worse having forked staffing of development teams is about as interesting to a large company right now as letting users have free access to an iPad without a SOE lock down. The reality is right now any adoption bet a company makes is likely to be repaved post Windows 8 sales begin as weird as that sounds? If you look at Windows 8 today you’ll see the Google Chrome Logo color scheme spread out into a bunch of Boxes that are basically fluff for the consumer. A few people out there will get all excited about the Metro - err..Modern UI - style experience(s). Companies who have a solid bet on .NET however will be keeping a very close eye on how you can hijack the consumer experiences to suit their agenda(s). Just like in the Original XBOX or Kinect release in which Microsoft had expected the market do X in turn users ended doing mods/hacks to use it for their own needs. A company facing a mobility crisis as the one they are facing today will see past the mickey mouse Windows 8 UI layer and instead hijack it for their own needs. Giving users the ability to wet their appetite with .NET level code on Win8 devices will be enough to hold the door open in the potential “if we don’t build a mobile/web story our competitors and/or customers will kill us” door closing campaigns. That in itself is an interesting thought to let fester, what if Windows 8 saves the Enterprise from having to decide on HTML5/Android/iOS? What if the .NET kids simply keep pumping out a WPF like solution but on a device. Wait, I just looked around and it occurred to me. It’s already happening only downside is they need a way to kill off the Windows 8 AppStore experience and revert back to a “my app will be all you need for this new Surface hardware you have in front of you”. Windows 8 will have a yearly upgrade path, there will be a subscription model that works like it did with OSX Lion and if you combine both Apple payment ideas with Silverlight’s deployment model you have a fairly good enoug Windows 8 story that will keep Business occupied long enough for the merging of Windows Server 2008 and Windows Enterprise Customer Client Thingy story. I’d wager that if business does uptake on Windows 8 they will force Microsoft into a reactive situation where they’ll likely have to sacrifice features set for consumers only and instead opt for Enterprise (which is where they will make their unit sales through the most).
The calendar increments by 1 year now and as it does I think about the last year and ponder what I liked and disliked in my sandbox that I call the Microsoft ethos
Windows Phone 7
- I liked Nokias approach to branding the product; they really took what they saw and made it the focal point of what the experience for consumers should be. That is, they did what I asked at the start of the year; make the metro design your familiar face in the crowd.
- I liked the WP7 Design contest; I rarely ever give an endorsement to contests as they are a desperate response to bad marketing, in this case though the designs that came back were actually tidy and immediately wanted you to explore the apps. Now to see if they make it into the appstore.
- I disliked WP7 marketing from Microsoft, it was chaotic, it lacked depth and $500million in marketing spent later, I still can’t put my finger on one message that you could hang your hat on. Compare Apple iPhone / Android marketing to Wp7 and it baffles me as to what is going on in that team – I think they just carpet bomb SeaTac / LAX airports with it knowing that Microsoft Execs travel through there and hope that’s enough to convince them they are “everywhere” – reality is, Bus shelter ads aren’t putting the wp7 logo on the bottom of their “get our apps” signage – which is a fail.
- I disliked the WP7 app store pricing model, fact is they are charging the same rates as iPhone devs or there about and in the end you have a marketshare that Samsung is even beating. I agree with Laurence Moroney – Reality check for two please and can we have that to go.
- I disliked the compete b.s that came from Staffers at Microsoft around WP7, fight the internal metrics and rise above the whole “heh did you see that, Apple just copied us!” mentality. Its very weak and if you are to beat the competition then you need to stop watching their every move hoping and praying for a weakness to occur. If Apple copy you, great, internalize that victory but keep it internal and instead move the bar higher as the best way for people to absorb that reality is when someone who doesn’t have an MVP or Blue-badge says “Did Apple just copy Microsoft?”.
Windows 7 and 8
- I liked the intent for Microsoft to bring balance to the UX force, which is a consistent looking brand / feel across all products from now on.
- I disliked the execution of the consistent branding. I wished they would keep all design decisions in a central team, which is everything from website design to UI design(s) for products. Allowing individual teams within Microsoft to interpret Metro outside of the central team at this early critical stage is clearly not working. If you want to attract a design enriched audience that want to take inspiration from your work, stop farming it out to agencies who nickel/dime their way through design creation and instead double down on providing a central experience.
- I liked the energy that the Windows teams have around device development, we’ve asked for this way back in the days of Surface birth. I think that’s healthy for the industry and will put touch enabled devices into more and more people’s hands sooner rather than later.
- I disliked the artificial inflation of the metrics (Windows and Wp7). Inside Microsoft you gauge success based on your ability to ignore qualitative data and instead focus on quantitative given it looks bigger. This often spills over into the marketing engine(s) at Microsoft resulting in just bad reality checks thus creating more distance between the ability to trust anything the brand states.
- I disliked the development experience required to get access to the touch enabled world. A friend of mine sent me this break down of tag trends over at Stackoverlow, basically if you are working with Silverlight and/or WPF the chances of you not using Stackoverflow in some form of way is next to zero. WPF and Silverlight dead? Can I have an extra order of reality check for team Sinofsky please?
- I liked the notion that Windows 7 is on the rise over Windows XP, the growth you have is great, and the sooner we can stomp on the neck of Windows XP the happier my development sandbox will be.
- I disliked the fact that Windows 7 has a huge market share right now, today, that I can’t access and instead am told to “chill” until Windows 8 AppStore comes online via Windows 8. It’s like the Microsoft team decided “How else can I really fuck my customer base over” then some clown in the back puts his hand up and tells them of an idea to hold back AppStore whilst everyone just sits there nodding like he’s telling them that touch will be the future for Microsoft back in 2007 – oh wait… has anyone seen JJ Allard lately as that guys going places.
Silverlight / WPF.
- I liked the fact we got some releases for these products, shows there is still someone within the company stoking that release fire.
- I liked Silverlights new 3D capabilities, it hints at what could have been possible had we had it sooner. We back in the early days would often discuss how 3D would be our next frontier of innovation for the product and my hat goes off to the engineering efforts for pulling it off – they worked hard.
- I dislike that Silverlight release was late and I especially disliked the way it was done. Microsoft phoned in the release, let it happen in the dark of night instead of the grandeur we’ve been used to in the past. That for me sent a clear signal to the developer base – it’s time to move on, finish up your creations and wait for next shiny object to come to a install near you.
- I dislike WPF feature list, it was less than we were promised (technically it was more tease / flirt) and lastly the release itself was more of an internal upgrade spilled over onto external HDD’s – that is to say, the features were more derived from internal needs than external. MIC check, is this thing on, WPF is dead in the eyes of Microsoft but its far from dead in the eyes of your average .NET code jockey.
- I dislike the energy spent on HTML5 is the future, I’m yet to meet a developer who uses Silverlight/WPF get excited at the idea of abandoning this for HTML5. It must be the other developers I don’t’ see who want it – well that’s what we may be assuming amongst each and everyone one of us “must be the other guy needs it” (ie “Pretty girl syndrome”).
- I liked the SDK experiences that come with this ….product? … I think it is much easier at times than people give it credit for. I’ve used Amazon quite extensively this year and often will grow impatient that its not like Azure.
- I dislike the pricing models for Azure. I’m a fairly intelligent guy but even today I’d not say I can for certain grasp the pricing model needed for me to respond to a work order request from some of my clients (mining companies who pay very large sums of money may I add).
- I dislike the fact Scott Guthrie is running this only. In the short time he’s been the custodian of this product its gotten better, great, but Scott should be a higher power across all products. Steve Sinofsky you suck the life out of Microsoft development.
- I liked the way Bizspark program is breaking down the pricing barrier of entry for Azure, I was skeptical of this program when it first started (My office was near the creator of this program back in the day, wand watched its birth). I think this program is what stands between adoption and non-adoption but at the same time it has really piss poor marketing behind it so unless you know someone who knows someone, it needs more help (See Catherine Eibner in Microsoft Australia, she’s got her head screwed on tight around how this should work going forward. Promote her to lead the charge here).
I liked the fact IE6 is hated in a more formal fashion at Microsoft, but overall I just wish this product in its entirety would just die. Everyone else is embracing Webkit, stop fighting the obvious and bend over accept you lost proprietary way of life and jump into the stagnant waters of Webkit FTW.
- WCF team can rot in hell. I think there is enough issues around this product to simply state, stop what your doing and think about its effects on your audience. Until then, rot in hell.
- Entity Framework team, make a decision and stick with it or at least promote the reasons why you change APIs and their pro’s / con’s.
- Zune. Great idea, pitty it never left Redmond zip code.
- Surface 2 – Great idea, pitty it never left Redmond zip code.
- Bing. I googled Bing, enough said but the fact you didn’t have a Santa Tracker at Christmas – you are dead to me.
I got word of a leaked email early yesterday that confirmed what I had been told in passing gossip – the XAML team being disbanded.
This morning I awoke to not just one email but five of them from my various sources all attached with mixed opinions on what it means. Here is my famous (internally in Microsoft, I would send these style of emails about Adobe and their competitive threats) "What Just Happened" response.
We're pleased to announce the transition of the XAML
platform team from the Developer Division to the Windows team. While the
team has been working side-by-side with the Windows team for the entire project,
this step brings them into our team formally.
It is time to start moving the battleships into the attack formation. In that time to start the consolidation into the new ux platform we are about to remake again.
On the upside it means you have a consolidated outcome likely to hit our hard-drives in the next 2-3 years on the downside you have what I would call a technology freeze in effect. If the new iteration of WPF or Silverlight does not comply with the vNext vision, do not hold your breath for a new announcement anytime soon that does not involve Windows 8 future(s).
The team will continue their work on Windows 8 as planned
and will join our Developer Experience (DEVX) team. This transition allows us
to bring together our platform development team in a single-management
That doesn’t sound to bad, I mean on the surface its just a single management restructure. A day in the life of a Microsoftee where every fiscal year or often more than once you are given new managers because the strategy - scratch that – tactics have changed. That in itself is probably your biggest hint of all around the word commitment, this is not just a case of waiting for a restructure to occur once every 5 years – it happens often.
To clarify, do you keep swapping your generals around in war to the point where the troops effectively stop caring who they are reporting to? Probably not a smart idea but nonetheless.
The dev, test, and pm leaders who will be leading the
team reporting to AlesH, YvesN, and LindaAv are:
• Sujal Parikh, Development Manager
• Eduardo Leal-Tostado, Test Manager
• Joe Stegman, Group Program Manager
The leads and individuals joining our team are receiving
this mail and have received communication on next steps.
If most of you who have been involved in the Silverlight ethos are reading then the name, Joe Stegman will probably stand out the most. Joe’s background in the .NET space goes back a ways but in the end Joe’s really been one of the guys under the hierarchy crust of commitment pledges keeping things in the development side of things in check. Officiating his role further in this equation for me is a bit puzzling as it’s kind of the same thing different org tree?
These changes in leadership and organization are
effective today. For the purposes of finishing out the fiscal year and
the performance review process the team will operate under the existing
That is a swift maneuver. Nothing surprising though.
Now onto Soma’s email to the troops which kicked the previous email off (Notice how VP’s etc all pile on from one another with "what he said was.." like somehow being apart of the thread is being seen as a role of importance. Classic Microsoft Victory Email formula, just once I’d like them to send out just one email outlining the change. This is what I’m talking about when I say Microsoft Culture is retarded.
Over the last couple of years, our Client and Mobile team
has done a fantastic job of building a number of XAML related technologies that
have been a huge value add to the Microsoft client platforms and an
instrumental part of delighting our developer customers. The agility and
customer focus that the team has demonstrated over the years has been a
pleasure to watch.
Ooops. Btw this was supposed to be confidential. So do not tell anybody.
Over the last couple of years? From memory, I recall WPF being around for more than a couple of years? Never mind, I keep forgetting everyone internally has forgotten about WPF.
Soma is kind of saying, "thanks for the hard work troops, you managed to outpace most products in Microsoft with your constant brilliance around the word agility, which being said here comes the but to that placating statement.
Today, we are making some organization changes to bring
our platform technologies under a single management structure. These
changes are centered around three focus areas:
• The team working on XAML technologies for Windows will
move to Windows.
• The team working on XAML technologies for Windows
Phone, Xbox and browser plugin will move to Windows Phone.
• The Client and Mobile tools teams, including Windows
Phone tools and XAML tools, will stay in DevDiv.
These changes are all effective immediately. From a
performance review perspective, we will do this year’s performance review under
the DevDiv organization model.
"Today marks a new day troops, for we storm a new beach" is kind of the response to that next piece.
Firstly you have parts of the XAML team(s) parked inside the Windows organization. First impressions on twitter are that "Way to go! Means XAML and Windows are finally going to get along and create awesome XAML experiences"
Have I not shown you the Annie video? Moreover, have I discussed the Orphan Syndrome? "My dad’s going to come for me, he’s rich you…you..you just wait and see"
To me that read as being a case of cherry picking parts of the team to socket into the windows division and their new coding charter will come next. If it involves XAML it will be based around what XAML vNext is likely to be – HTML5 meets Jupiter.
Same with the Phone team, it is what I would call "please standby for further orders" moments.
As for the tooling teams, well you got Cider and Expression Blend team is what that really comes back to. Given most of the Client employees have left, I am not sure what that means suffice to say I am not holding out for a new release for Sketchflow for starters and I am guessing that the Blend teams are not exactly getting high fives for poor sales and download rates to date. If I were in that team, I would be updating my LinkedIn account quickly.
I want to thank Kevin Gallo and the team for all the
great work that they have done over the years. Moving forward, I'm very
excited to bring the client platform efforts closer to the platform
teams. There is a lot of very exciting and critical work underway as part
of our next wave of platform releases and I am very eagerly looking forward to
seeing the team’s work in the hands of our developers and customers.
Remember when Mary Jo posted a while back on how Kevin Gallo would be taking over the reins of Scott Guthrie. That’s probably the quickest promotion and I’m not ready to say demotion but I’m not ready to say continuance either – that I’ve seen?
The positive part there is the "next wave of platform releases" that sounds a lot like a continuation of what we have in front of us. Make no mistake there will be a Silverlight 5 and a WPF vNext released next fiscal, its already got most of the code done and it would be foolish to not release those when they can – especially after MIX2011.
Releasing those two would also buy you time for the next 2 fiscals at most. As by doing this you create this calming effect around "see, we’re still working on it..honest" to placate the developer hordes.
That is up to you, you can buy into that sure, and it is hard to debunk given there is not much visibility behind what we are likely to see next – especially given this is tradition within the Microsoft roadmap(s).
For me personally, I’d like to corner Microsoft If I could into giving more concrete assurances that whatever the next wave of bets are that they are either backwards compliance or have parity around what we have today in terms of conceptual features today.
Features for me are not will I be able to still hit F5 without changing code. Features for me are the concepts that are on the table today, around how one manages the out of browser and in-browser functionality – everything from casual gaming through to enterprise ready features (printing, isolated storage, data binding etc).
I think what has happened in this email is the equivalent of me saying "I really like this car, now can we take the wheels and put them over there. In addition, can you take the steering wheel and dashboard and put it over there. Lastly, can you take the engine and well. Just leave it in place for second; I’ll get back to you later on where we can put that next"
It’s clear there is a consolidation happening that I think we can all agree on early. How will the consolidation impact the average .NET developer is likely to be dramatic enough to warrant some applications having to have code refactored down the track – you will not escape that sorry.
Does this mean .NET is dead? Who actually knows what .NET vNext will be so it is hard to simply say "yes" and it could very well be a reset of .NET to fix a lot of pent up frustration in the way it sticks together today.
What I am certain of is WPF is definitely officially done. The chance of WPF going beyond what it is today is slim. Some journalists etc. will gloss over this as its not news but let me be clear in saying at Microsoft we really had no clue just how deeply seeded this product became.
In Australia it’s used quite heavily and it’s something I personally noticed whenever I used to travel around the country meeting Microsoft customers (both as an Evangelist and Product Manager). I used to send emails internally stating "I think we underestimated is usage, as it definitely appears to have more devs using than Silverlight" which was later brushed aside as being "Not realistic".
I think post September the announcements that are to follow will give these warnings probably some second thoughts around what parking WPF in the retired bay is likely to mean for Microsoft when it comes to the words "trust" and "commitment"
The product and developer satisfaction surveys for the last few years haven’t been something you’d brag about internally which for me indicates a strong sense of "fatigue" within the ranks of our beloved .NET developer communities.
It’s now one thing to announce what the next version of .NET will be its entirely different thing to convince and sell these fatigue customers that this is defiantly the bet this time. Silverlight, WPF and WinForm are available today and millions are shipping software solutions using them.
Microsoft now has to figure out a way to convince the millions that the "Windows 8" wave of vNext will fix all of these problems and more – and – will not require a reduction in feature parity along with extra boost in tooling.
If I know, my Microsoft and I like to think I do, good luck J
Full email below:
From: Julie Larson-Green Sent: Monday, June 20, 2011 9:35 AM To: Grant George; Jon DeVaan; Julie Larson-Green; John Cable; Yves Neyrand; Craig Fleischman; Bambo C. Sofola; Scott Herrboldt; Greg Chapman; Julie Bennett; Jeff Johnson; Ales Holecek; Mohammed El-Gammal; Chuck Chan; Michael Fortin; Eric Traut; Jensen Harris; Linda Averett; Alex Simons (WINDOWS); Gabriel Aul; Dennis Flanagan; Iain McDonald; Samuel Moreau; Dean Hachamovitch; Michael Angiulo; Antoine Leblond; Tami Reller; Chris Jones (WINDOWS LIVE); Jonathan Wiedemann; Ulrike Irmler; Adrianna Burrows Cc: XAML Team; Kevin Gallo; S. Somasegar; Terry Myerson; Sharman Mailloux Sosa; Brad Fringer; Steven Sinofsky Subject: Please welcome the XAML platform team to Windows! We're pleased to announce the transition of the XAML platform team from the Developer Division to the Windows team. While the team has been working side-by-side with the Windows team for the entire project, this step brings them into our team formally. The team will continue their work on Windows 8 as planned and will join our Developer Experience (DEVX) team. This transition allows us to bring together our platform development team in a single-management structure. The dev, test, and pm leaders who will be leading the team reporting to AlesH, YvesN, and LindaAv are: • Sujal Parikh, Development Manager • Eduardo Leal-Tostado, Test Manager • Joe Stegman, Group Program Manager The leads and individuals joining our team are receiving this mail and have received communication on next steps. These changes in leadership and organization are effective today. For the purposes of finishing out the fiscal year and the performance review process the team will operate under the existing management structure. There will be an informal Q&A session today to welcome everyone and answer any questions that folks might have. • XAML team welcome – 2:00-3:00 in building 37/1701 Please join me in welcoming these folks to our organization! Julie From: S. Somasegar Sent: Monday, June 20, 2011 9:16 AM To: Client and Mobile Team Cc: Developer Division FTE; Steven Sinofsky; Julie Larson-Green; Terry Myerson; David Treadwell Subject: Bringing together client platform efforts MICROSOFT CONFIDENTIAL Over the last couple of years, our Client and Mobile team has done a fantastic job of building a number of XAML related technologies that have been a huge value add to the Microsoft client platforms and an instrumental part of delighting our developer customers. The agility and customer focus that the team has demonstrated over the years has been a pleasure to watch. Today, we are making some organization changes to bring our platform technologies under a single management structure. These changes are centered around three focus areas: • The team working on XAML technologies for Windows will move to Windows. • The team working on XAML technologies for Windows Phone, Xbox and browser plugin will move to Windows Phone. • The Client and Mobile tools teams, including Windows Phone tools and XAML tools, will stay in DevDiv. These changes are all effective immediately. From a performance review perspective, we will do this year’s performance review under the DevDiv organization model. I want to thank Kevin Gallo and the team for all the great work that they have done over the years. Moving forward, I'm very excited to bring the client platform efforts closer to the platform teams. There is a lot of very exciting and critical work underway as part of our next wave of platform releases and I am very eagerly looking forward to seeing the team’s work in the hands of our developers and customers. The follow-up emails will provide more details on the changes to those impacted. Please join me in wishing Kevin and the team all the very best as we move forward. If you have any questions about this change, please let your manager or me know. -somasegar
I did it! and I feel exposed. I sat down tonight and put together my first of what may or may not be many (depending on how badly I get crit) screencasts around UI / UX + Microsoft Technology.
In this video, I show folks how one can take a workflow design concept and inject it into your canvas of choice but in an Isometric format. I like Isometrics simply because you can get more of a spatial view than most screen angles that and it derives from my old Pixel-art days so..yeah..Isometrics are the way!
Hope you enjoy, and feedback welcomed.
In this screencast I show how one can take a Isometric workflow map and transpose it into Expression Blend 4.
WPF Time of Death.
Time to call it, December 2nd 2010. Seriously, I have thought about the Silverlight Firestarter event for a few weeks now with a focus on reading how the rest of the world kind of digests the vNext of Silverlight.
Its very clear if you read between the lines that Silverlight is shaping up to replace the WPF workload, and whilst Microsoft will roll out the engineers + shipping routine its pretty much all they aren’t doing before WPF is officially declared dead. Shipping is realistically the one thing they have left and even that’s looking a bit sketchy and cumbersome to watch.
It’s clear with Silverlight5 my old comrades in arms at Redmond have even stopped paying lip service to the x-platform discussion with many of the new features being Windows specific. It’s also clear given Windows Phone 7 failing in the market that now is not the time to give Microsoft’s biggest competitor, Apple momentum or face an internal career firing squad.
WPF has enormous amount of hidden potential, its not marketed but its there. It’s not a bad desktop platform to build against and majority of the issues that I have personally faced with the product are due to basically quality assurance sloppiness. Its still got work-around solutions though, so you in turn forgive it’s sins.
Technically being ok is not enough though, you need to go wide and far in promoting its existence and the return on investment you could potentially yield from the platform. That's not happening and its also clear that there’s zero paid community evangelism efforts in market right now to uphold this line of thinking.
An example, Where is the WPF fire starter Microsoft? where is any event for that matter that focuses on exploring the bounty of WPF?
Scott Guthrie’s blog is typically a marketing announcement channel given his geek-fame over the years. It’s often we in marketing would joke (sarcasm) “its a good thing we have ScottGu’s blog, as boy we almost needed an official marketing site for Silverlight” – jokes aside, Scott doesn’t talk about WPF at all (check out the below tag cloud)
If i were to audit Microsoft today online and tally up WPF vs. Silverlight, which would win? Argue with the notion that something is dead or isn’t but its definitely clear that WPF hasn’t a bright future as its technology cousin – Silverlight.
Windows Phone 7 – Fail.
I have predicted that I think WP7 is going to not win consumers over but I figured that it would take a couple of years before that is realized. Hearing reports that the device has small units of sale and now some resellers are slashing prices in a hope to stimulate the market to buy, is just downright disappointing.
Its not that the phone is bad, its actually got a load of potential. As whilst I’m a WPF fan at heart, I do still also enjoy working with Silverlight (which has this kind of polarizing effect on me). I just think that the Metro User Interface is simply killing the products potential.
It’s important to call that out, given this is the “face” of the brand. It looks tacky, not well thought out and clearly lacks usability principles needed to navigate a small device. It puts to much emphasis on typography and downplays visual elements to provide structure and grouping to the components within (ie Extraneous Cognitive Load).
The keyboard is to primitive and the keys are narrow. I’ve sat down and looked at the iPhone and Wp7 keyboards and for me the WP7 looks like a prototype version of the concept. The keys don’t necessarily guide you to aim for the middle, where as the iPhone keys are spaced but at the same time the hit area isn’t exactly confined to that space. You in turn are more likely to focus on your target even though the spacing is artificial.
Typography is weak and at times doesn’t even do the basics – in outlook a list of bold means new, unbold means read, yet you still don’t even get this? The menu system is a endless vertical nightmare, as whilst its great to list things its important to also balance out your screen between scrolling and displaying. I find the constant scrolling down to be cumbersome and annoying especially when you’re debugging an Application you’re writing for the phone.
I could list more and I’ll be talking 1:1 with Wp7 Product Management, but i think my point here is made, this phone needs more energy and focus. It has enormous potential ahead of it but for the space price or thereabouts as its biggest 800lb gorilla competitor is simply unrealistic. Lower the price or fix the UI, make a choice as the UX for Microsoft is dying as-is. Which brings me to my next point.
Designers aren’t interested anymore.
If you look at the AppStore market place, majority of the apps are visually engaging and have definitely some design bloodlines in the room. If you look at the Microsoft marketplace its pretty clear that designers aren’t in the room in large quantities.
No designers means wasted technology, wasted technology means some team internally right now is coming up with the “fix” for this (which in their minds is an engineering problem not an engagement problem). The reality is you can throw all the tools you want at this problem as well as the platforms, but unless you truly evangelize in a non-aggressive way to this market. You’re just wasting good money on technology that goes nowhere.
If you were to compare 2007/2008 Evangelism efforts to present, You would see this massive disconnect between strong in your face marketing to the art community to today being a bunch of engineers high fiving one another about how awesome things are. The reality is, unless you can add some design blood lines to this new UX driven world, your technology hasn’t moved forward, you’re just rebadging old technology with much weirder UI.
Silverlight 5 is WPF’s new replacement, and I really don’t have that much of a problem with this other than if you’re going to make this the vNext desktop focus, then commit. Don’t do it half-assed, get those 200+ engineers and get your butts into gear and open it up more. If you aren’t going to do this, then take 100+ engineers out of that 200 and get them to focus on doing more with WPF so that the two are more aligned to save cross-targeting related issues – as news flash Redmond, nobody really thinks that far ahead as to which technology is likely to give them an outcome they desire. Choosing Silverlight first then hitting a wall and retreating back to WPF is unrealistic as it means people need to know its faults completely end to end and how these map to their business constraints upfront? sorry no.
Windows Phone 7 needs something. It needs a more structured approach to user experience and it needs to solve WPF and Silverlights initial problem – how to get designers to the cause. Unless Microsoft gets off their butts and re-invest into the designer focused communities, these products are destined to follow the same non-starters as previous incarnations of the Windows Phone operating systems as well as the low saturation levels in the wild of both Silverlight/WPF publically.
“There are certainly some functionality shortfalls, and we are going to work to address them,” – Joe Belfiore / Microsoft.
Microsoft needs to get back to evangelism 101 and more importantly the notion that just because you ship doesn’t mean you’re committed to the future. Creating features and releasing them isn’t enough, unless you broadcast and win the hearts & minds over all you’re effectively doing is having a bunch of engineers in Redmond high five one another over a release that could be epic if it got momentum – FAIL.