no, I rethinked about that, I'm disturbed by the circular bullshit here:
1) my website need to do computationally intensive tasks, so need wasm to do it efficiently.
2) I dont provide a interpret-based fallback becasue I dont intend to provide my service trough it, I choose wasm as a requirement.
3) lets put another giant piece in the chrome codebase just to inefficiently interpret code that is not intended to be interpreted.
I dont think is bad overall that chromium and vanadium adopt it, I think that a code project that add this kind of stuff with this kind of logic is doomed to ever be insecure, frequently zero-dayed, less and less manageble and customizable by third party (and individual users) and a giant pile of uncomprensible garbage.
Chromium is at one more giant new commit to solve the security problem as government is at one more regulation to solve inflation