rsrc VS fynedesk

One problem is, on Windows, this is impossible without bundling your application with a compiled manifest (I use github.com/akavel/rsrc. It's a horrible state of affairs brought about by backwards compatibility, but without it when you ask for a version, you'll get Windows 8 no matter what.

https://github.com/akavel/rsrc/ - could take some support for version info - it's probably currently the most requested feature in it; as to UX my preference would be for passing it via JSON; some basic barebones tests would also be good, I mean to roughly verify that the version actually gets added successfully, via some powershell/vbscript script or something;

When embed data to Go binary, need to prepare syso file. There is a tool called rsrc that will generate syso file for embedding in the rsrc section, so let's use that.

We (I am one of the developers) also have https://github.com/FyshOS/fynedesk as a desktop environment.

If U like a Go Desktop try this: https://github.com/fyne-io/fynedesk

The Oberon channel has several videos of Oberon in action,

https://www.youtube.com/results?search_query=The+Oberon+Chan...

While Oberon was quite cool, people should also learn about its Xerox influence,

"Eric Bier Demonstrates Cedar"

https://www.youtube.com/watch?v=z_dt7NG38V4

Also dive into what happened afterwards, Oberon-2, Active Oberon, Zonnon,...

Active Oberon could be considered quite modern, also makes the distinction between safe and unsafe pointers, which improves the experience for low level coding.

https://github.com/metacore/A2OS

One of the best things about these systems is proving what systems programming with automatic memory management were capable of.

Given Oberon-2's influence on Go, maybe improving Fyne (https://fyne.io/fynedesk/) with something like gRPC for the dynamic experience, could be a possible sucessor.

The thing is with go is it's kind of made for web applications. It's made by google for google. Taking a look at the standard library you can see the most fleshed out parts are for general system access, networking and particularly http, and crypto. People have obviously made things outside of those scopes like fynedesk, but that's where the focus of golang is.

Another angle for when a toolkit is mature could be when it’s used for a full desktop environment :). MacOS and Windows native toolkits obviously tick the box. GTK+ has Gnome, Qt powers KDE (both have Go bindings), Enlightenment is powered by EFL (no Go support yet). Fyne is being used for FyneDesk https://github.com/fyne-io/fynedesk

One other idea that I had: There are new approaches to the desktop like e.g. FyneDesk, a *nix desktop environment written in Golang (using its own GUI toolkit). It's BSD-licensed (3-clause) and I would expect the team being more than happy with anybody trying to make it available to a wider audience. Might be worth a thought.

100% agree on the theming, quick glance at the current implementation seems to indicate hardcoded values (I am assuming this is an early spec) https://github.com/fyne-io/fynedesk/blob/master/theme/theme.go

we were thinking of contributing to this project fyne-io/fynedesk: A full desktop environment for Linux/Unix using Fyne (github.com)