I agree this is an important consideration but the overheads here are getting smaller and smaller. The Python binary (a whole language runtime!) on WAPM is sitting at 5mb. Right now the median desktop page weight on HTTP archive is about 2mb. So not that substantial an increase, plus it'll get cached.
The classic way to instantiate WASM was to grab all the bytes, then instantiate it over multiple steps. This can now be done in streaming mode, meaning it'll happen as the binary downloads. This is much simpler and faster!
When you compare it to something like video playback it's not really that bad at all. Just feels bad because this isn't how things have been done historically.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree this is an important consideration but the overheads here are getting smaller and smaller. The Python binary (a whole language runtime!) on WAPM is sitting at 5mb. Right now the median desktop page weight on HTTP archive is about 2mb. So not that substantial an increase, plus it'll get cached.
The classic way to instantiate WASM was to grab all the bytes, then instantiate it over multiple steps. This can now be done in streaming mode, meaning it'll happen as the binary downloads. This is much simpler and faster!
When you compare it to something like video playback it's not really that bad at all. Just feels bad because this isn't how things have been done historically.