There aren’t really much PWA/front end libraries for Go, despite being a strong backend language. I am curious to see how Go would compare with JS considering that WASM exists, and Go has GopherJS and Yew. Also would it be faster than JS if it were browser-native?
Disclaimer: I have not tested WASM, but as I understand it will it be slower to load initially.
- type constraints
- code shedding (only packs codes that I need)
- Re-use my Go library as much as possible
- PWA compatibility (offline and online modes)
I can see the next evolution is server-side only offers API while client-side performs user interface rendering and operations, especially given the current geo-political reasons and warfare =( ; and E2EE requirements (e.g. Bitwarden).
FYI: I will begin full WASM exploration starting next month intending to upgrade my hugo theme module into full CSR frontend library.
Well, I would not hope to much in this direction mainly because WASM programming is very complicated than the classical even if we are talking about JS and suppose a big effort even to do small things. I suppose that this is the reason because is not wide spread nowdays.
Besides, it’s quite obvious the original intention was to replace JS. However, this will trigger tech political uprising among the JS community so it was changed to complimentary. As you know, when politics involves, everything is expensive and slow.
If Autodesk can bring AutoCAD (Roundup: The AutoCAD Web App at Google I/O 2018 - AutoCAD Blog - Autodesk) to the cloud without too much changes (https://web.autocad.com/login), heck, I’m convinced with the investment.
Besides, we’re not limiting to Go. C, Rust, or other proper programming languages can go on-board with WASM.
Yeah C and Rust can also be used, but I just love how Pythonic Go looks like and how batteries-included it is. Rust seems too hard, and C is like Bugatti: really fast, but lots of maintenance needed with nulls, memory, etc.
Also, I wonder if there’s a Phoenix Liveview backend only web app framework for Golang.