The article seems to evaluate Wasm as it were a framework upon which apps are built. It's not that, it's an orthogonal technology allowing CPU optimisations and reuse of native code in the browser. Against that expectation, it has been a huge success despite not yet reaching bare-metal levels of performance and energy efficiency.
One such example: audio time stretch in the browser based upon a C++ library [1]. There is no way that if this were implemented in JS that it could deliver (a) similar performance or (b) source code portability to native apps.
We absolutely do need regulation of this harm by the law. It's how we stand together as a society, otherwise one child's rules will seem draconian against their friend's lax parents. There's plenty of precedent in other threshold ages at which children can start indulging in other potentially harmful vices.
The vulnerable elder population is more difficult to define by a simple age threshold. We all decline at different ages and different rates.
One such example: audio time stretch in the browser based upon a C++ library [1]. There is no way that if this were implemented in JS that it could deliver (a) similar performance or (b) source code portability to native apps.
[1] https://bungee.parabolaresearch.com/change-audio-speed-pitch