WASM is run in a "brain in a jar" type execution model, with basically zero knowledge or access to its external environment (the "host"). So it could absolutely take advantage of these kinds of peripherals, but the host enviornment would provide import functions that enable it to interact with resources like a video card.
The gap is definitely closing as you say, and WebAssembly provides a path for it, as well as a security model that doesn't put users at risk.
Idk what the parent comment was, but I'm guessing it's the "REAL code runs in binaries" or "there is no cloud" you see sometimes around here. Best not to take it personally.
haha I don't take it personally, but I do think people deserve to be called out when they are flagrantly disrespectful not only to the individuals who work on the primary project, but the second-order disrespect to people around the world advancing capabilities of the web and making technology more accessible.