> The only way it really fell short is in the way that a lot of people were predicting that it would become a sort of total replacement for JS+HTML+CSS for building web apps.
I for one hope that doesn't happen anytime soon. YouTube or Spotify could theoretically switch to Wasm drawing to a canvas right now (with a lot of development effort), but that would make the things that are currently possible thanks to the DOM (scraping, ad blockers etc.) harder or impossible.
> DOM (scraping, ad blockers etc.) harder or impossible.
This is a cat mouse fight, and Facebook already does some ultra-shady stuff like rendering a word as a list of randomly ordered divs for each character, and only using CSS to display in a readable way.
But it can't be made impossible, at the worst case we can always just capture the screen and use an AI to recognize ads, wasting a lot of energy. The same is true for cheating in video games and many forms of online integrity problems - I can just hire a good player who would play in my place, and no technology could recognize that.
I can't speak for FB. But I know a local (non-US) real estate company which does crap like this (they also love to disable right click and detect when browser tools are open and programmatically close the tab/page when that happens), and they're not paying much. I'm guessing it's double of minimum wage, which isn't high here.
Perhaps require monitoring of the arm muscle electrical signals, build a profile, match the readings to the game actions and check that the profile matches the advertised player
You are probably right. What will happen is that ad-blocker people will indirectly kill accessibility. That would make a lot of sense in this world. Its a reoccuring pattern. Spam killed a part of accessibility indirectly via CAPTCHA. And "it is my god-given right to block ads of free services I use" people will indirectly finally kill accessibility for good, now that we have <canvas>.
Yes, however I reject the idea that a full WASM app would be strictly worse for accessibility in the long term. Native UI frameworks do have accessibility APIs and browsers could implement something similar.
So far, huge rewrites/rearchitecturings typically worsened the end user experience from an a11y POV. I even know people personally who have lost their job of 20 years because their employer decided to redo their IT, "accidentally" leaving the disabled employee behind. It is naiv to think a big rewrite will NOT make things much worse for years.
I for one hope that doesn't happen anytime soon. YouTube or Spotify could theoretically switch to Wasm drawing to a canvas right now (with a lot of development effort), but that would make the things that are currently possible thanks to the DOM (scraping, ad blockers etc.) harder or impossible.