4 ms·

Actually, we have recently improved on this, it’s probably now less than half an hour of setup, at least on Linux. The new guide is on the Github repo: https://

Actually, we have recently improved on this, it’s probably now less than half an hour of setup, at least on Linux. The new guide is on the Github repo: https://gist.github.com/nehbit/4a8c3d81d543e85c9df974f521732b1e https://gist.github.com/nehbit/4a8c3d81d543e85c9df974f521732... We use Electron exclusively for GUI. The real app is a Go binary with a GRPC API. It’s all fully isolated, so if you don’t want to touch any Electron, you don’t have to. Use the API to build a CLI app, for example. To be more specific, we have two Go binaries that we ship, one is the aether-backend that talks to the network, the other is the aether-frontend that compiles the content coming from the network into a social graph. Both are properly isolated and talk to each other only over declared GRPC APIs. I’ve tried very hard to keep it hackable that way.

0x6c6f6c 6y ago
There's a fully JavaScript implementation of gRPC[0] that you may be able to use should you implement a web app using Service Workers[1]. This would be installable for browsers in a manner that should provide long-lived access to the network. 0. https://www.npmjs.com/package/@grpc/grpc-js https://www.npmjs.com/package/@grpc/grpc-js 1. https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers https://developer.mozilla.org/en-US/docs/Web/API/Service_Wor...
LockAndLol 6y ago
> Both are properly isolated and talk to each other only over declared GRPC APIs. I’ve tried very hard to keep it hackable that way. That's a great architecture! I look forward to hacking on it when I have the time!