I switched from Java to Go some 3 and a half years ago. When I was going through The Go Programming Language (Kernighan et al.), I thought I’d just skim the chapter on packages. In Java, at least, it's a relatively unremarkable topic—something you don’t spend much time thinking about.
But Go is different. Interestingly, Go packages made me think more deeply about code organization than Java packages ever did.
The more I reflected on Go packages—especially while writing this article—the more they made sense. And to be honest, I think Java should reconsider some of its package conventions, as they might be one of the reasons for its "notorious" verbosity.
But Go is different. Interestingly, Go packages made me think more deeply about code organization than Java packages ever did.
The more I reflected on Go packages—especially while writing this article—the more they made sense. And to be honest, I think Java should reconsider some of its package conventions, as they might be one of the reasons for its "notorious" verbosity.