Alex RussellLearn to spot, and write off, the Hacker News trope that real problems with real frontends aren't real problems for actual users because Rust and WASM will save us.
You cannot make this shit up:
Ben Delarre@slightlyoff hah. Well at least you got the cookie consent pop-up in around 6s! ;-)
@bendelarre 26MB of WASM to order a 🍕? We should all be so lucky!
@slightlyoff that's... Impressively wasteful. How do you even manage that? We deliver Photoshop in less!
westbrook@slightlyoff But, it's an example...just imagine how much more code when it ACTUALLY orders a pizza!?!
@westbrook I don't know what's in the 9.5MB `ordering-system.data` file that load after the 26MB WASM bundle, but at this point I'm afraid to ask.
Paul Mason@slightlyoff @westbrook The pizza. 😒
@paulhmason @westbrook ...smells like anchovies.
@slightlyoff @bendelarre That 26mb of wasm will cost more to download than the pizza in some countries. There was a very good reason why Polymer was so popular with African software developers (and Flutter, but not for web).
@slightlyoff @bendelarre But seriously, that's almost an order of magnitude larger than Blazor (wasm), which is already an unbelievably antisocial thing to inflict on a person.
Jenniferplusplus@slightlyoff this is what it looks like on mobile when it finally loads (which took about 4 seconds for me)
jerry@slightlyoff that's some thick pizza slices
haz@slightlyoff no way this is real..
Thomas Steiner 
@slightlyoff Interesting how the text inputs don’t trigger the virtual keyboard to appear. There’s no way to use this.
Noam Rosenthal@tomayac @slightlyoff specifically for Qt-related things, the use case is more as a portability layer for desktop UI rather than something meant for everyday webapps. I think that's the most valid use-case for WASM. (and yes it's far from mature when it comes to input handling)
Kenji Baheux has moved@noam @tomayac @slightlyoff this somewhat reminds me of how bad things were with CJK input method editors with PPAPI Flash in Chrome. It took a lot of energy to get back what should have been a must have in v1 :/ I hope we don't end up with another cycle of "viable in [slice X of the world/users]" products...
@kbx @tomayac @slightlyoff yes, it’s a very similar set of problems. Though eliminating the previous solutions didn’t make some of those use cases go away 🤷🏻♂️
Johan Halse@hejsna the trashfuture is here, it's just not evenly distributed yet