Without Windows Mobile, UWP is no longer Universal... what was the point of years of engineering Windows OneCore... when Windows Group got to the end of the effort, "politicians" killed off Mobile platform... despite their "mobile-first" strategy, fools
developer community is in need of humanitarian relief more then ever from mental anguish caused by dilapidated assembly language targeting low level browser runtime that has been prosecuting us since 1995...
Bring out the Eliminator-4000 to our aid 😀 and let's put end to our collective suffering
Thank you for explaining the tremendous amount of engineering effort done to make .NET (CIL) run on new form of Windows Runtime. The investment in this infrastructure piece of work allows mortal C# developers to write code in easy to understand language; and all the heavy lifting done by native compilation toolchain. Work as this can only be done by Microsoft; and is good to see teams at Microsoft pushing .NET Applications to run on more platforms... including mobile scenarios; which are battery and CPU constrained... so again, C# developers do not have to think too much about those issues.
Please continue to invest in infrastructure engineering efforts; solving very difficult problems.
Agree, Java Swing does indeed looks shitty everywhere...LOL... however, there are better examples to model on... Silverlight (ran on Win & Mac) was built with XAML (style + layout) on top 2D rendering capabilities. WPF arguably did not use native Win32 or GDI+ on Windows for drawing, but rather vector graphics, again had a rendering surface.
Ask: Build cross platform 2D rendering surface for .NET Core (an infrastructure piece)... if Microsoft does not have resources for higher level UI widgets/controls... let community or 3rd party UI components partners build UI widgets/controls on top .NET Core cross platform 2D rendering surface.
Edit: Office team may already have cross platform 2D "know how"... as they had to deal with rendering document/spreadsheet/powerpoint content on Android and iOS
Value that Prism offers is immense... far too many developers have constructed "big ball of mud" without any code structure. Prism provides simple way to apply proven patterns and practices for building extensible, module and maintainable .NET application that can evolve with requirements, and withstand test of time. Having architectural guidance such as Prism improves image of solutions build in .NET. Application without necessary code structure look like a product written by struggling amateur.
Practicing concepts contained in Prism library, help me to build better server side code (modularity, component discovery), and be more effective software developer. I consider Prism essential part of any professional .NET application developer toolbox!
Very glad to hear about potential of Regions available on WinRT and Forms.