Makes sense to move the window system glue parts on a different 'track'.
IME the window system glue is the actually ugly and maintenance heavy part when writing a cross-platform 3D API wrapper. The various core 3D APIs (D3D, Metal, Vulkan, even GL) all map to the same hardware so it's quite trivial to get them to do the same thing.
But for the window system glue it gets ugly. Different platforms and window systems don't agree on how 3D rendered surfaces should be presented and how frame-pacing is supposed to work, there's a fundamental conflict between event-driven UI apps and frame-driven 'game-y' apps, the window system glue generally seems to get less attention than the core 3D APIs (maybe because it sits exactly between areas of responsibility), there are sometimes subtle behaviour changes between operating system updates (especially on macOS), and let's not even mention Wayland.
The result is that the code which sits between the window system and 3D rendering becomes an accumulation of experiments, hacks and workarounds, has a very high churn and in the end those 10% of the code base suck up 90% of the work :/
It is amazing to see what is happening with wasm/wasi lately and that is all grew out of asm.js.
asm.js, like JSON, is a strict subset of the JavaScript grammar that turned out to be very useful in a certain way. Obviously, a text encoding like asm.js wasn't an efficient way to distribute a bytecode, but it proved enough to make wasm the obvious next step.
Everyone keeps forgetting NaCL and PNaCL predates it, and asm.js only exists because Mozilla didn't want to adopt it.
And this was the one time Mozilla was right ;)
Somewhat dubious claim if it was right or not, the only benefit was that asm.js was backwards compatible and set the stage for Mozilla to lose out by simply having the slower JS engine whereas NaCL/PNaCL proposal was "performance neutral" between browsers.
For what, Firefox is for all practical purposes irrelevant in a Chrome dominated Web, Google can steer WebAssembly into whatever direction fits Chrome.
I have finally realised that the year of true WebAssembly breakthrough will coincide with Desktop Linux of the year and GNU Hurd installed on every toaster. It will be a strange year ...
The Year of Desktop Linux already arrived, except not as originally expected.
It turned out to be The Year of Desktop Linux VMs/containers, on someone's else desktop OS.
Makes sense to move the window system glue parts on a different 'track'.
IME the window system glue is the actually ugly and maintenance heavy part when writing a cross-platform 3D API wrapper. The various core 3D APIs (D3D, Metal, Vulkan, even GL) all map to the same hardware so it's quite trivial to get them to do the same thing.
But for the window system glue it gets ugly. Different platforms and window systems don't agree on how 3D rendered surfaces should be presented and how frame-pacing is supposed to work, there's a fundamental conflict between event-driven UI apps and frame-driven 'game-y' apps, the window system glue generally seems to get less attention than the core 3D APIs (maybe because it sits exactly between areas of responsibility), there are sometimes subtle behaviour changes between operating system updates (especially on macOS), and let's not even mention Wayland.
The result is that the code which sits between the window system and 3D rendering becomes an accumulation of experiments, hacks and workarounds, has a very high churn and in the end those 10% of the code base suck up 90% of the work :/
It is amazing to see what is happening with wasm/wasi lately and that is all grew out of asm.js.
asm.js, like JSON, is a strict subset of the JavaScript grammar that turned out to be very useful in a certain way. Obviously, a text encoding like asm.js wasn't an efficient way to distribute a bytecode, but it proved enough to make wasm the obvious next step.
Everyone keeps forgetting NaCL and PNaCL predates it, and asm.js only exists because Mozilla didn't want to adopt it.
And this was the one time Mozilla was right ;)
Somewhat dubious claim if it was right or not, the only benefit was that asm.js was backwards compatible and set the stage for Mozilla to lose out by simply having the slower JS engine whereas NaCL/PNaCL proposal was "performance neutral" between browsers.
For what, Firefox is for all practical purposes irrelevant in a Chrome dominated Web, Google can steer WebAssembly into whatever direction fits Chrome.
I have finally realised that the year of true WebAssembly breakthrough will coincide with Desktop Linux of the year and GNU Hurd installed on every toaster. It will be a strange year ...
The Year of Desktop Linux already arrived, except not as originally expected.
It turned out to be The Year of Desktop Linux VMs/containers, on someone's else desktop OS.