Yes, the size of the binary is quite big (~4MB for the landing page) but it's a trade-off that I'm taking with this approach and I think there will be ways to optimize for size.
I'm currently using the built-in WASM target but Tiny Go is one of the items that I have on v1.0 road map. Will give it a shot and see if it actually helps with the size without affecting any performance.
I'm building a Go to WASM reactive UI framework called Goowee. Fine grained signals (no VDOM), components run once, SSR and hydration built in. The JS bridge is about 200 lines. Still experimental but I've thought about it thoroughly and have used it for the landing page of the project and some other projects of mine.
I know Go UI frameworks have a long history of not quite getting there. The bet I am making is that WASM is now fast enough, the tooling is mature enough, and the fine grained signal model avoids the VDOM overhead that held earlier attempts back. Would love an honest critique of whether the framework actually solves the problem and whether it's usable for other's development experience.
I'm currently using the built-in WASM target but Tiny Go is one of the items that I have on v1.0 road map. Will give it a shot and see if it actually helps with the size without affecting any performance.