couple of month ago I had the exact same idea (go wasm vue) and thought it was good because shrinking the tech stack reduces costs and WASM brings additional potential.
If we had hot reloading, reactivity, virtual rendering/DOM and templating in one web frontend framework written in go that would be pretty nice.
A go web API server could be its companion.
In this scenario a dev could concentrate on improving his/her go skills and only needs DB-querying and CSS skills alongside (and that'd be all needed for a reactive database driven web application)
Nice you've found the time for this POC, keep it up and make the repo public ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Jeff,
couple of month ago I had the exact same idea (go wasm vue) and thought it was good because shrinking the tech stack reduces costs and WASM brings additional potential.
If we had hot reloading, reactivity, virtual rendering/DOM and templating in one web frontend framework written in go that would be pretty nice.
A go web API server could be its companion.
In this scenario a dev could concentrate on improving his/her go skills and only needs DB-querying and CSS skills alongside (and that'd be all needed for a reactive database driven web application)
Nice you've found the time for this POC, keep it up and make the repo public ;)