@christianweyer and @endocrimes you can continue the threat on #webassembly and #dotnet here. (was : https://twitter.com/christianweyer/status/1601909248115474434?t=CpOh7oI-gTl61Zfei5T0GQ&s=19)

@flavio_castelli got his wasm down below 9MB, I think, but without asp.

Christian Weyer (@[email protected]) on Twitter

“@endocrimes @ralph_squillace Thx! This gives me a 28.7 -> 25.8 MB "improvement" for a Hello World #AspNetCore Web API project (release build) 😉”

Twitter
@christianweyer @endocrimes @flavio_castelli in any case, @stevensanderson is the expert here....
@squillace @christianweyer @endocrimes @flavio_castelli If you enable trimming the default ASP.NET Core app wasm size is about 13MB IIRC. And you can change the initial memory allocation with a clang flag - 32MB is enough. None of this is documented of course, as it’s unsupported yet.
@stevensanderson @squillace @christianweyer @endocrimes @flavio_castelli from what I experienced, with some aggressive wasm-opt it is possible to reduce the size even further. for a no frills console app (which runs on Cloudflare) it was possible to get ~3MB quite easily
@filipw @squillace @christianweyer @endocrimes @flavio_castelli True! You can push it as far as you want, just depends how much functionality you need. I got C# Hello World down to 80KB compressed using the normal runtime, or 8KB using a zerosharp-like approach. But that’s only for demos. Realistic apps will likely be in the megabytes.
@stevensanderson @squillace @endocrimes @flavio_castelli Trimming brings it down to 10.9, and wasm-opt to 8.2MB.
Thanks!