I blogged my thoughts - Xamarin & Microsoft merger may yet prove useful to designers. http://www.riagenic.com/archives/2005 - I'm not to impressed with the "developer" gains here, as in the end whether its Xamarin or UWP running the show, the trick is to get a .NET developer to have parity in terms of design/development capabilities as they had with WPF/Silverlight/UWP whilst on x-platform/x-device... at the moment there's still way to many IF/ELSE moments occurring for that to naturally happen which imho poisons the well.
--- Regards, Scott Barnes http://www.riagenic.com On Fri, Feb 26, 2016 at 7:55 AM, Ian Thomas <il.tho...@outlook.com> wrote: > It’s those “more considered” comments to Guthrie’s blog that I think are > worth looking at. I’m not sure if comments determine any actions, though. > It’s probably direct contact with Microsoft people to discuss the > short-comings and the wish-list that would be more productive – but as I > wrote, I found some of the comments interesting. Not just the fact that MS > had acquired Xamarin. > > > > > > Ian Thomas > > Albert Park, Victoria 3206 Australia > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Greg Keogh > *Sent:* Friday, 26 February 2016 8:49 AM > *To:* ozDotNet <ozdotnet@ozdotnet.com> > *Subject:* Re: Microsoft acquires Xamarin > > > > Oh yes, and if you read here: > > > > https://weblogs.asp.net/scottgu/welcoming-the-xamarin-team-to-microsoft > > > > As they suggest, fix the pricing and fix the bugs - *GK* > > > > On 25 February 2016 at 22:48, Ian Thomas <il.tho...@outlook.com> wrote: > > Everyone will know this in 2 days of course, but Microsoft has finally > bought Xamarin > <https://weblogs.asp.net/scottgu/welcoming-the-xamarin-team-to-microsoft>. > > Just who (employees, developers) from the company will transition across > to MS is not clear. > > There are some interesting comments to this post; not unexpectedly, > reflecting (for one example) Greg Keogh’s reticence in adopting it at its > cost for effective development by in dependent developers. And its > efficacy. > > It’s not clear how it will be made available to the levels of Visual > Studio licensing (cost), but it seems more than sensible to me to make it > available at a modest subscription cost – perhaps not with Community > Edition. > > > > Ian Thomas > > Albert Park, Victoria 3206 Australia > > > > >
