What benefits does this have over Electron?

Why why would I want to use Go on the integration side, and still have to use JS within the webpage? Most Electron apps I've seen have a slim wrapper of code in their main file to just initialize native things. Why is it better or easier to do that in Go instead of in JS?

>> Why would I want to use Go

Probably, you wouldn't. But it's not quite surprising if users of GopherJS and Go would prefer Go over JS, is it?

Picking your technology stack based on "what you prefer working with" rather than "what works best for the application you're building" is piling on technical debt before you've even started your project. That isn't saying Gallium is necessarily the wrong choice over Electron; it's saying you should evaluate them both and use the one best suited to what you're building, even if that means learning a new language.

(Obviously this is a ideological argument rather than a practical one because most projects don't have the budget for devs to do that much prep work like learning a new language, but practicality is boring. :) )

Isn't Electron the very definition of "Picking your technology stack based on what you prefer working with" rather than "what works best for the application you're building"?

I think Electron has proven to be a very powerful model for GUI customization IMO. Some of the plugins people are building are truly amazing and I can't see this happening in a non-web ecosystem.

Can you give an example or two?