Is there something fundamental in Go's symmantics that prevents dynamic linking? Or is this just a tooling issue? Personally, I think I might avoid a language

Is there something fundamental in Go's symmantics that prevents dynamic linking? Or is this just a tooling issue? Personally, I think I might avoid a language that defined how the end product could be packaged, that just seems outside the range of what a good language should focus on. Go definitely bucks the trend in modern web age language development,for starters it generates raw binaries. That alone puts it in a different category than just about everything else of significance that has been developed over the last decade. Rather than coming out with a full auto-completing IDE from the start or a plugin for netbeans or eclipse, they've got a lightning fast object code compiler. The natural evolution of these things is to get raw binaries working, get the langauge pretty much stablizied, then add some default libraries and tools to make shared libraries and get dynamic linking and PIC code type stuff working and the language shouldn't have to actually change for that to happen, you just change the tools and create different ways to compile stuff. I'd expect shared libs to come along.