Respect any attempts to make a nice web framework in Go. But I prefer the Gin routing API and the ORM seems disjointed from migrations. I'm not sure what's the purpose of WASM; I know Blazor is trying and it's having scalability issues. And you mentioned mobile app, but I didn't see anything in the docs.
back
1 comments
getting there. Docs are v0.0.1 for sure. WASM means no more javascript! You can write all your frontend dom manipulation in go.
That's what Blazor WASM promises too. Last time I checked people were saying that initial load times were quite slow though.
I personally would recommend focusing on ORM, Auth, and an Admin panel to replace Django. JS isn't as much of an issue because you often end up needing it anyway.
go ahead and try this site that's in production:
notice the: <script>document.addEventListener("DOMContentLoaded", function() { const go = new Go(); WebAssembly.instantiateStreaming(fetch("/assets/other/json.wasm.gz?id=1EBB13D9-6DBB-4E2F-89A6-D40F0C456B3D"), go.importObject).then((result) => { go.run(result.instance); WasmReady('space.html'); }); });</script>
at the bottom of the html. ALL the client side stuff is golang wasm. Is it slow?
Nope, seems pretty quick. Well done!