Great post! I wonder if you have considered the legal implications of statically linking the Qt/QML LGPL library. The normal suggestion to remain ok legally to sell one’s creation is to make sure to dynamically link and ship the library unaltered with your own application object code. Go, of course, creates a single statically linked object file making it convenient to distribute. Does this violate the LGPL? Seems like it does. If so, any Go application that uses Qt could never be sold based on the default static linking approach. The issue is a larger one related to Go because the LGPL depends so heavily on dynamic linking and Go so conveniently does static linking.