Man... If anything, I have to say I am very pleased with how much work Team Brian has put into getting XF support into Prism. I honestly didn't think it would ever happen... or be the typical EntLib cadence of a few years before we heard anything. Even though we might disagree 100% where Xaml is best utilized (smile), the fact that we're using is what is important. It is THE superior mechanism of defining applications and nothing in the technology landscape comes close to it (imo). I'm glad we are talking/debating Xaml and not HTML5, which is what we (or a majority of us) would be using if Xamarin.Forms was not around as a cross-platform solution. I spent about a year and a half in HTML5 and it was not pretty. There were some pretty dark years these past few years, but that is no longer the case. The light is here once again, and it might be even brighter than silver this time around (see what I did there?).
Anyways, coding is fun again. It's exciting and promising, too. The fact that a staple technology like Prism is already on-board with XF only adds to the awesomness.
Now, if Team Brian can get the rest of EntLib onto the hotness, everything will be right with the world. :)
Anyways, coding is fun again. It's exciting and promising, too. The fact that a staple technology like Prism is already on-board with XF only adds to the awesomness.
Now, if Team Brian can get the rest of EntLib onto the hotness, everything will be right with the world. :)