News for hackers. Stuff that matters.

A comment on How Four Native Developers Wrote an Electron App. Parent comment

Re:How Four Native Developers Wrote an Electron App by WorldMaker on Friday May 19, 2017 @12:08PM (#14377011)
Win32 is essentially deprecated and the native toolkit from Windows 8 on is the WinRT components/engines in "Windows.UI.*" which natively speak XAML (and natively here means these are C++ components baked into the OS). WPF has much more in common with the modern Windows.UI toolkit than Win32 does.

DirectX is at the same level of abstraction as Win32's Graphic Device Interface (GDI) and Hardware Abstraction Layer (HAL) that the rest of Win32's "native toolkit" was built on top of; Windows.UI is just as "native" as Win32 ever was. It should not be a surprise that the hardware abstraction toolkit beat into performance submission by performance demanding games is the new native layer for Windows. The surprise should be how long it has taken to make the transition across. (Avalon promised it back in Vista and WPF was the closest to delivering it. Windows 8 finally delivered on the Avalon promise.)

[ Parent | on HN ]
Re:How Four Native Developers Wrote an Electron App by flukus on Sunday May 21, 2017 @08:22PM (#14390078)
The problem is they didn't provide backward compatibility for Windows.UI. Until windows 7 is dead win32 is the only native option.
[ Parent | on HN ]
Re:How Four Native Developers Wrote an Electron App by WorldMaker on Monday May 22, 2017 @11:18AM (#14394269)
I think to some extent they felt WPF was a strong enough backward compatibility story. Windows 7 supports WPF well. There is a cross-over between WPF XAML and UWP XAML and it is possible to support both with a lot of code shared and even some XAML shared.
[ Parent | on HN ]
Re:How Four Native Developers Wrote an Electron App by WorldMaker on Monday May 22, 2017 @12:29PM (#14394891)
Of course, there have been bumps in the road in the compatibility story between the two XAML environments. .NET Standard 2.0 will help a ton (in the very near future), deeply increasing the amount of .NET code that can be shared between the environments. XAML Standard 1.0 (in the slightly further future) will help a lot, in particular the fact that Xamarin.Forms is planning to implement a WPF renderer for sharing a much larger portion of XAML across every platform.
[ Parent | on HN ]