What does HackerNews think of go-plugin?

Show HN: Togomak – declarative pipeline orchestrator based on HCL and Terraform | Oct 2023

I am looking forward to a mix of both - I am hoping to add a concept called "operator" which would be a go-plugin [1], just like terraform providers, but build backends. So, someone would be able to, say, write a Slack plugin (in Go, or anything over RPC) which sends a message once a build is complete - like Jenkins/GitHub actions, or just scripts that we can reuse like GitLab CI through `modules`.

Perhaps a new registry where we can push custom modules and providers (operators in this case), I'm curious to know about if we have any existing implementations we could reuse for the registry.

[1]: https://github.com/hashicorp/go-plugin

Choosing Hashicorp go-plugin in 2023? | Jul 2023

For some reason, the act of choosing a plugin mechanism for our new project has been presented in my head a dilemma. Not a clear winner between the built-in stuff (plugin stdlib), the boring but battle tested option (Hashicorp go-plugin [1]) and the new exciting shiny ("future proof?") object web assembly plugins [2]

I ended up choosing the "traditional" Hashicorp library but any feedback, or comments on why you might think I am making a terrible mistake would be appreciated :)

[1] https://github.com/hashicorp/go-plugin [2] https://github.com/WebAssembly/WASI/blob/snapshot-01/phases/...

Wazero: Zero dependency WebAssembly runtime written in Go | Jul 2023

Expand Context ↕

Have you looked at https://github.com/hashicorp/go-plugin?

Ask HN: What is your “I don't care if this succeeds” project? | Feb 2021

Expand Context ↕

I benchmarked some of the most popular go plugin libraries here in addition to the plugin package that comes with go: https://github.com/uberswe/go-plugin-benchmark

Right now I'm leaning towards using https://github.com/hashicorp/go-plugin

You should link your project, it would be interesting to follow.

Traefik, Now With Native Go Plugins | Sep 2020

Does anyone have time to explain the downsides of the HashiCorp plugin approach (gRPC to another process) vs. creating an interpreter?

https://github.com/hashicorp/go-plugin

Go command support for embedded static assets (files) | Jul 2020

Expand Context ↕

https://github.com/hashicorp/go-plugin

If you squint it’s reminiscent of zeromq for IPC :)

You can contrast that with https://golang.org/pkg/plugin/

Golang Package: plugin | Sep 2016

I agree with this comment from Reddit four days ago:

> The inability to unload a plugin defeats the use I would have for this, unfortunately. A long running service with plugins may want to load new, updated versions of an existing plugin. Not being able to unload the old version, ends up creating stale references which will keep piling up for the lifetime of the process. As I understand it, this is essentially a memory leak. [...]

> https://www.reddit.com/r/golang/comments/53adu8/a/d7rmmco

There is also this project by Hashicorp: https://github.com/hashicorp/go-plugin

Microservices with Go, go-microservice-template and Minke | Mar 2016

HashiCorp is working on something like this: https://github.com/hashicorp/go-plugin