Brad Peabody
Brad Peabody
Another aspect of this is supporting automatic updates for executables. Since Go is great at producing single big binaries instead of lots of little files, it means it could be...
As it stands right now, this is a bit outside the scope of what Vugu is intended to do. There are many things that you can only accomplish in Wasm...
Sounds good. This article has a bit of example code that might be helpful: https://www.aaron-powell.com/posts/2019-02-06-golang-wasm-3-interacting-with-js-from-go/
Figure out Wasm Binary Diff/Patch for Caching Parts of Wasm Binaries; or Domain-Specific Compression
Another observation on this is that the wasm code emitted right now by the Go compiler uses a loop algorithm http://troubles.md/posts/why-do-we-need-the-relooper-algorithm-again/ to allow the necessary jump/resume functionality to get things...
Figure out Wasm Binary Diff/Patch for Caching Parts of Wasm Binaries; or Domain-Specific Compression
It would also be really helpful to have an analysis tool which showed what functions and packages were consuming the most space. Disassembling a program and just measuring the byte...
Work in progress: https://github.com/gotailwindcss/tailwind
Thanks for this. Yeah the vugufmt code is a bit out of date, needs some TLC. I'll leave this open to address the next time maintenance is done on that...
@itschrono There's a lot that goes into the [rendering code](https://github.com/vugu/vugu/blob/master/domrender/). Whatever solutions will have to be carefully considered.
Okay, thanks for reporting, will look into it when I can.
@owenwaller I'm pretty sure it's related to this change: https://golang.org/doc/go1.16#go-command > Module-aware mode is enabled by default, regardless of whether a go.mod file is present in the current working directory...