This sounds like something that was a good idea to begin with - we should ensure the libraries can be MIT licensed by using a separate binary, then hitting the "most likely go developers don't want to setup a complex C++ compile chain" to "I known we will just precompile it" to "oh but where can I download it from" to "oh I have that server".

Every step in the chain makes sense and is done with the best intention, but the result is, well.

Been there done that. Didn't get the t-shirt.

Reminds me of PS/Tk, a cross-platform, cross-implementation GUI library for Scheme that worked by opening a pipe to a Tcl/Tk process and communicating with that. It actually worked fairly well, though it's sadly abandoned now. I contributed somewhat by getting it working for Gambit.

Do you mean that it was abandoned for Gambit? It's available for Chicken [1] and via Akku [2] for Chibi, Gauche, and Sagittarius.

[1] https://wiki.call-cc.org/eggref/5/pstk

[2] https://akkuscm.org/packages/(rebottled%20pstk)/

Jia Tan, is that you?!

Yea.. that sounds like a non-starter for use.

> Yea.. that sounds like a non-starter for use.

I'd also wager that a FLOSS binding to a non-FLOSS framework with steep licensing fees would also kill this option for most.

What non-FLOSS framework do you mean? Qt Widgets is LGPL,