4 ms·
The key takeaway is this: Personally, I'm too entrenched in the Obj-C/iOS ways to develop my own, personal Metro app. But based on what I've seen about Metro,
by AshFurrow 15y ago
The key takeaway is this: Personally, I'm too entrenched in the Obj-C/iOS ways to develop my own, personal Metro app. But based on what I've seen about Metro, I can see a lot of Enterprise ASP.Net corporate developers going home at night to tinker on their Metro apps, and who can argue against that?
- gary__ 15y agoWPF, (the modern way to create .NET windows client UIs) and Silverlight/Windows Phone 7 development is done using XAML at the minute so those developers would have the best head start. Note, it was probably Visual Studio 2011 you saw, 2010 has been out for a while.
- AshFurrow 15y agoOh, you're right - thanks! I'll correct it.
- icefox 15y agoThe end of the conclusion really doesn't relate to the article. It starts with "Let's face it: Metro will be a success.", but they he talks about how he has no plans to develop for it.... which is not success in my opinion. Three days of them showing you everything (probably with free food too and access to devs) and it isn't impressive enough for you to make an app what makes you think other devs in mass numbers will develop for it?
- AshFurrow 15y agoHere's the thing: I'm a long-term mac user and a developer for iOS. The training didn't include any XAML training; any interface design was copy-and-paste because writing the XAML wasn't the point of the training. If I was a .Net developer in my day job, I would be writing a Metro app right now.
- MatthewPhillips 15y agoThe C#/Xaml stuff is for WPF and Silverlight developers. HTML5/JS is the obvious choice for everyone else.