purego VS hlive

Click here to view the commit: https://github.com/ebitengine/purego/commit/1a4ea678b5a7598275a28e787179da1b7a058b11

Click here to view the commit: https://github.com/ebitengine/purego/commit/1a4ea678b5a7598275a28e787179da1b7a058b11

Maybe interesting for you: https://github.com/ebitengine/purego

most X11 functionality can be accessed via xgb|xgbutil (jezek has a current fork). nucular makes use of it via shiny. OpenGL and such libraries can be assumed to exist on those systems, so directly calling those c libraries without cgo is a possibility. Ebiten is currently working on it: purego.

In the malware reverse engineering scene, there are a lot of forks of the upstream "debug" go library, because it allows loading, parsing, compiling and executing libraries from disk (rather than in-kernel or in-userspace).

And there's also "purego" as an implementation that directly generates shellcode.

Maybe those will help you, too?

I am just mentioning these because for my use cases those approaches worked perfectly, CGO free.

[1] https://github.com/Binject/debug

[2] https://github.com/ebitengine/purego

https://github.com/ebitengine/purego Instead of Go using C toolchain, purego bypass it for already (should I say compiled or object-compiled)

You could use https://github.com/ebitengine/purego which would not require a C compiler to build

I do a lot of wired stuff with server-side virtual DOM, and I've found Go a good fit. I don't think inheritance is a problem with designing a component library. I've used struct and interface embedding to share common functionality. (see Tag and Tagger, then Component and Componenter as sort of examples).

Poking through the repo at https://github.com/SamHennessy/hlive now. It's particularly interesting to me because I wanted to write a virtual DOM for something that did serverside rendering and clientside via WASM. I wanted to be able to parse a template language much like jsx or Angular templates for a delcarative syntax. A friend of mine I worked with years ago and I set up a 3 day hackathon. We went through some design work, decided we didn't have time in our lives to take on a project like this, and settled on using Go's html templating. I tried to reuse a lot of the concepts using a two pass method (since you can't hook into the parsing but can always register DOM listeners) thinking I could accept a little inefficiency in exchange for a lot less work. Finally, the weekend was over. We had some interesting ideas collected with some innovative new thoughts on state management, but he dove into his next project using Vue instead, and I haven't had time to continue.

I'd appreciate it if you tried to build something using this: https://github.com/SamHennessy/hlive