@mauve
> Be minimal (fewer built-in features, leave more to the OS)
Yup. My markdown viewer (mvu) was implemented with webkit and gjs. Well, it works fine, but I'm not so happy with gjs, it feels too much like Java. :( I never came to use it as a front-end for everything. Still too clunky..
@gert I feel you on gjs. I was looking into using it at one point too. I think the thing I keep struggling with is that I want apps I make to be cross platform but all the options for that kinda suck or are limited for the protocol handlers use case. Right now I've been dreaming of Rust and maybe forking Servo.
@mauve What if we disconnect the GUI from the middleware and only let it talk to e.g. curl. Then we can put the protocol layer between them and make one extra data hop (e.g. on unix sockets). Which might slow things down, but not noticeable.
Could work either with webkit + gjs or https://servo.org/ + rust.
@gert That's not far from what I've been doing in Agregore actually. All the protocol handlers are runnable as daemons without too much trouble and I actually used a local gateway for the Godot support in HyperGodot. Been thinking of figuring out how to bundle the protocol stuff into something easy to install.
@mauve Brilliant, That puts your Agregore browser on my radar.