Didn't one of the main selling points of Go is one big static executable with no external dependencies?
What's next? Generics?
What's next? Generics?
This is not like dynamic linking hell you can get yourself into when writing C.
So basically something like apache modules - either you can load the module or not - vs something like "cannot find symbol foo in foo.so.0.1."
In my Go code, I've just used subprocesses for that. Stdin & stdout, plus a simple serialisation format, and I'm done.
Not suitable for high performance stuff, of course, but good enough for my needs.
No, but they will eventually need to handle plugin versions.
Because that doesn't sound very reasonable to me, even after ignoring that plugins aren't really dependencies anyway.