>Regressing by ~10x isn't a compelling argument. If it's loading faster than user "consumes" assets, it doesn't matter how fast it is. It's not different for n

>Regressing by ~10x isn't a compelling argument. If it's loading faster than user "consumes" assets, it doesn't matter how fast it is. It's not different for native games that allow you to play earlier than the whole thing finishes downloading. >And you somehow don't see the problem? Don't stupidly update the entire thing every time? Send deltas? Don't update as often? As for not having background updates it's a minor issue anyway (I for example don't start Steam unless I'm going to play), and there are Progressive Web Apps and Service workers to solve this issue. >You don't have to suffer the web's treadmill of being a decade+ behind to have that. Whoever needs the latest features can of course use a native platform. For developers who don't need the latest features or especially heavy graphics, WASM+WebGPU will be a viable option. That's all. >You can both be a native game and get all the benefits of it and not pay anyone an app store fee! And the user has to risk trusting me executing native code, which would definitely lower conversion rate.