11 ms·

Note that it will download around ~300Mb of data directly to your browser, so it might take a bit to load from slow connections. Here's the related video from

Note that it will download around ~300Mb of data directly to your browser, so it might take a bit to load from slow connections. Here's the related video from FOSDEM: https://fosdem.org/2022/schedule/event/lotech_lowa/ https://fosdem.org/2022/schedule/event/lotech_lowa/

lokedhs 5y ago
Even with a fast connection, it takes a very long time. I'm guessing the site is overloaded as the peak was a few tens of Mb/s, and generally much slower.
- Epa095 5y ago
  Makes me wonder if it is possible/usefull to make the download a two step process, first download a small wasm bittorrent client, then use it to download (and share) the 300mb file.
  - hobo_mark 5y ago
    Webtorrent already exists, and does not require wasm. https://github.com/webtorrent/webtorrent https://github.com/webtorrent/webtorrent
    - LtdJorge 5y ago
      Could WebRTC be used directly here?
  - RReverser 5y ago
    Or it could apply gzip/brotli + optionally wasm-opt and cut the size ~5-6x: https://twitter.com/RReverser/status/1494435774003093515 https://twitter.com/RReverser/status/1494435774003093515
- vanviegen 5y ago
  It took about 20s for me, with the fans spinning up around halfway through. Once loaded it feels fairly usable, considering...
- mofosyne 5y ago
  Does make you wonder what other optimization can be done. Maybe the whole thing doesn't have to be loaded in immediately.
  - dspillett 5y ago
    Such lazy loading might be difficult to retrofit into an application designed for an environment where it can load a lot from disk to RAM quickly and has never (IME) been well design in terms of such resource use. Some lazy loading could probably be done relatively easily where OO does on-demand load libraries, but that would significantly resource apparent in-use performance if truly done live so you'd want to background load the optional parts once the immediately needed ones are done. I'm guessing that this is a straight compile to WASM with the minimal changes needed to things that would otherwise break completely in the different environment.
    - GeorgeHahn 5y ago
      Autodesk has shared some information about how they solved this when building AutoCAD Web, which is a wasm app derived from their desktop codebase. Video: https://www.infoq.com/presentations/autocad-webassembly/ https://www.infoq.com/presentations/autocad-webassembly/
kingcharles 5y ago
Appreciate the warning for those of us on non-wired connections!
rtpg 5y ago
Might be worth changing the link from the direct link to this video, given that 300 megs question.
ceasesurthinko 5y ago
And it's throttled too, took me ~8 min on a 400mbps connection to download those 300mb of data. And it doesn't cache the download either, so refreshing the page forces you to download the entire thing again.
- jack_pp 5y ago
  took me < 35s on a 300mbps connection from europe.
deathanatos 5y ago
300 MiB. & … "a bit" — it takes nearly 20 seconds on "Gigabit" fiber. (312 MiB in 19.22s, or 136 Mbps.) Runs shockingly smoothly once it starts, though.
- mynameismon 5y ago
  Funny, it took me approximately triple the time on a 60 Mbps connection. Makes me wonder if its throttled from source due to a network overload.
  - LeanderK 5y ago
    yeah, 300mb is not nothing but also not that much. Using full speed it shouldn't take that long.
- comboy 5y ago
  Progress bar would be nice, without these comments I would have no idea whether to wait or not thinking that maybe it got stuck in a loop downloading the same thing over and over again or something.
  - cyanydeez 5y ago
    when i built my webapp with tons of packages, i tried to figure out if we could hook into the browser, but theres really no way that i found, my solutioj was to just make webpack split the bundles into chunks then have them announce themselves and a loading screen would tally
  - a9h74j 5y ago
    Haven't explored higher-up pages. Eventually, would be nice if there were a way to download everything to one directory and run offline. Is this only a demo for now?
- sgjohnson 5y ago
  > Runs shockingly smoothly once it starts, though. On what hardware? I've got a 2019 MacBook Pro with i9 and 32 GB of RAM, and there's a noticable delay (I'd guess 200~400-ish miliseconds) when clicking any elements with Firefox or Chrome.
lanyusea 5y ago
took me 2 hours to load... LOL
deleted 5y ago
[deleted]
RReverser 5y ago
The sad part is, it could be cut very easily cut down to ~60MB with basic optimization & compression (heck, even gzip/brotli compression alone would go a long way): https://twitter.com/RReverser/status/1494435774003093515 https://twitter.com/RReverser/status/1494435774003093515 Impressive feat, but I'm worried this small detail ruins the first impression for way too many.
- syrusakbary 5y ago
  Damn, you are 100% on point. I assumed it already had the optimizations applied and it was big just because of the nature of the app. Once they get their server bill perhaps they will reconsider optimizing it!

lokedhs 5y ago

Even with a fast connection, it takes a very long time. I'm guessing the site is overloaded as the peak was a few tens of Mb/s, and generally much slower.

Epa095 5y ago
Makes me wonder if it is possible/usefull to make the download a two step process, first download a small wasm bittorrent client, then use it to download (and share) the 300mb file.
- hobo_mark 5y ago
  Webtorrent already exists, and does not require wasm. https://github.com/webtorrent/webtorrent https://github.com/webtorrent/webtorrent
  - LtdJorge 5y ago
    Could WebRTC be used directly here?
- RReverser 5y ago
  Or it could apply gzip/brotli + optionally wasm-opt and cut the size ~5-6x: https://twitter.com/RReverser/status/1494435774003093515 https://twitter.com/RReverser/status/1494435774003093515
vanviegen 5y ago
It took about 20s for me, with the fans spinning up around halfway through. Once loaded it feels fairly usable, considering...
mofosyne 5y ago
Does make you wonder what other optimization can be done. Maybe the whole thing doesn't have to be loaded in immediately.
- dspillett 5y ago
  Such lazy loading might be difficult to retrofit into an application designed for an environment where it can load a lot from disk to RAM quickly and has never (IME) been well design in terms of such resource use. Some lazy loading could probably be done relatively easily where OO does on-demand load libraries, but that would significantly resource apparent in-use performance if truly done live so you'd want to background load the optional parts once the immediately needed ones are done. I'm guessing that this is a straight compile to WASM with the minimal changes needed to things that would otherwise break completely in the different environment.
  - GeorgeHahn 5y ago
    Autodesk has shared some information about how they solved this when building AutoCAD Web, which is a wasm app derived from their desktop codebase. Video: https://www.infoq.com/presentations/autocad-webassembly/ https://www.infoq.com/presentations/autocad-webassembly/

kingcharles 5y ago

Appreciate the warning for those of us on non-wired connections!

rtpg 5y ago

Might be worth changing the link from the direct link to this video, given that 300 megs question.

ceasesurthinko 5y ago

And it's throttled too, took me ~8 min on a 400mbps connection to download those 300mb of data. And it doesn't cache the download either, so refreshing the page forces you to download the entire thing again.

jack_pp 5y ago
took me < 35s on a 300mbps connection from europe.

deathanatos 5y ago

300 MiB. & … "a bit" — it takes nearly 20 seconds on "Gigabit" fiber. (312 MiB in 19.22s, or 136 Mbps.) Runs shockingly smoothly once it starts, though.

mynameismon 5y ago
Funny, it took me approximately triple the time on a 60 Mbps connection. Makes me wonder if its throttled from source due to a network overload.
- LeanderK 5y ago
  yeah, 300mb is not nothing but also not that much. Using full speed it shouldn't take that long.
comboy 5y ago
Progress bar would be nice, without these comments I would have no idea whether to wait or not thinking that maybe it got stuck in a loop downloading the same thing over and over again or something.
- cyanydeez 5y ago
  when i built my webapp with tons of packages, i tried to figure out if we could hook into the browser, but theres really no way that i found, my solutioj was to just make webpack split the bundles into chunks then have them announce themselves and a loading screen would tally
- a9h74j 5y ago
  Haven't explored higher-up pages. Eventually, would be nice if there were a way to download everything to one directory and run offline. Is this only a demo for now?
sgjohnson 5y ago
> Runs shockingly smoothly once it starts, though. On what hardware? I've got a 2019 MacBook Pro with i9 and 32 GB of RAM, and there's a noticable delay (I'd guess 200~400-ish miliseconds) when clicking any elements with Firefox or Chrome.

lanyusea 5y ago

took me 2 hours to load... LOL

deleted 5y ago

[deleted]

RReverser 5y ago

The sad part is, it could be cut very easily cut down to ~60MB with basic optimization & compression (heck, even gzip/brotli compression alone would go a long way): https://twitter.com/RReverser/status/1494435774003093515 https://twitter.com/RReverser/status/1494435774003093515 Impressive feat, but I'm worried this small detail ruins the first impression for way too many.

syrusakbary 5y ago
Damn, you are 100% on point. I assumed it already had the optimizations applied and it was big just because of the nature of the app. Once they get their server bill perhaps they will reconsider optimizing it!