To me it seems as though the whole web assembly project early on adopted a motto that it was not going to do many UI or device related tasks.
I think that was for three reasons. A) it made the project much more feasible and B) the UI stuff was not necessary to achieve most of their goals.
But C) is that it made it un threatening and therefore something that JavaScript developers could accept since it "was not supposed to replace JavaScript".
What seems to be completely missing still from things like WASI is a serious and useful approach to UI and various non-file devices.
There should be something like a device driver API that various types of devices can plug into along with a few devices starting with a 2d graphics API of some sort.
I think that was for three reasons. A) it made the project much more feasible and B) the UI stuff was not necessary to achieve most of their goals.
But C) is that it made it un threatening and therefore something that JavaScript developers could accept since it "was not supposed to replace JavaScript".
What seems to be completely missing still from things like WASI is a serious and useful approach to UI and various non-file devices.
There should be something like a device driver API that various types of devices can plug into along with a few devices starting with a 2d graphics API of some sort.