[aryehof]

Helpful article thanks. My concern with Go is that it particularly suited to problems in the space of computing, and computer and data science. Like C, suited to systems programming. What I am unconvinced about yet, is how suited it is to problems that require the modeling of concepts and their interactions, an area well suited to object domain models outside of that sweet spot. I'm aware that the alternative to an object domain model, is a database model driven by use case based procedural code, which Go could be argued to be well suited towards.

Is the "package" as the unit of encapsulation a limitation that makes Go unsuitable to the large scale modeling of concepts in problem domains outside of the "computer"?

[christophberger]

Go is a pragmatic language, designed for programmer productivity. I think Go was never meant to be used as a language for reasoning about models and concepts at various abstraction levels and for arbitrary problem domains. There are certainly other languages available that are better suited for this.