One more thing. Be careful of "object oriented" design if you are thinking about shared libraries and re-usability. Depending on your definition of "object orie

One more thing. Be careful of "object oriented" design if you are thinking about shared libraries and re-usability. Depending on your definition of "object oriented" and the language you pick, it actually causes tighter coupling between components because the type system often encourages everything to be related. Since you mentioned Go, Go's approach to object-oriented tends to use interfaces which tends to avoid this problem. But your milage will vary depending on the popular semantics of whatever language you choose and also the conventions library writers use if you choose to use pre-existing libraries.