News for hackers. Stuff that matters.
Re:Caddy 0.9 Released with All New Core by spriggan3 on Tuesday July 19, 2016 @10:49AM (#12122094)
> What Go does not allow, is putting Go code into dynamic library and then calling that from another go application - i.e. native go plugins for go apps.

That's exactly what I said, you're talking about dynamic linking not dynamic library loading.

Re:Caddy 0.9 Released with All New Core by vetinari on Tuesday July 19, 2016 @11:03AM (#12122168)
It allows dynamic loading, but only C code, not Go code. You can do dlopen()/LoadLibrary() and then dlsym()/GetProcAddress(), but only with C calling convention.
Re:Caddy 0.9 Released with All New Core by spriggan3 on Tuesday July 19, 2016 @11:18AM (#12122253)
> It allows dynamic loading, but only C code, not Go code. You can do dlopen()/LoadLibrary() and then dlsym()/GetProcAddress(), but only with C calling convention.

That's a C feature not a Go one. You still can't do that ie calling a Go compiled library from a Go executable AT run time, like one can load JAR and execute some Java code from a Java program at runtime. Because the language doesn't allow that.

No matter how you people try to spin that thing this is impossible to do with Go directly. Period. Using C involves a crazy overhead and complexity which is absolutely not worth it.