3 ms·
I've been work on a proof of concept with Wails and it's a productive development loop. The only thing different about the front end code vs a website is that i
by cheriot 4y ago
I've been work on a proof of concept with Wails and it's a productive development loop. The only thing different about the front end code vs a website is that it calls functions generated from my Go back end (fully typed!) instead of making an HTTP call.
The end result is a single binary. I suspect there's interesting things to be built as small extensions/compliments to command line tools.
- dopamean 4y agoThis sounds really cool and makes me want to learn go so I can make some desktop apps...
- afavour 4y ago> The only thing different about the front end code vs a website is that it calls functions generated from my Go back end (fully typed!) instead of making an HTTP call Now take it to the next level: put those functions in a service worker and create a REST API that works entirely locally and can be switched out for a remote server with ease. Or don’t, if you have no intention of making a web version. But IMO it’s a powerful model for those who do.
- cheriot 4y agoThat's an interesting point about service workers. My thinking is to layer them in the other order: the generated types are based on Go struct json tags so the function signatures I'm calling could be implemented as REST calls. ie SomeEndpoint(paramA: string, paramB: string): Promise<SomeEndpointResponse> The notion of a web version is a distant one for the current project so it's only a theory.
- hogyncymraeg 4y agoNot...that...far... :-)