pkg/ inside of Go projects. It is just like any other sub-package structure you might otherwise define in your project. It just adds an extra part to your imports. I think it's actually confusing at best and just unnecessary typing and an unnecessary sub-structure. Just keep your packages in the top-level and be done with it 👌
@prologic@twtxt.net I’m bad with terminology, sorry. But I think, we’re basically on the same page. The only thing I wanted to say is, that I fully agree with @brasshopper@twtxt.net’s theory here and tried to elaborate a bit.
Even if you have a very deep knowledge of one language, you typically won’t know about all the styles, patterns, spirits, etc. when starting to pick up a new one. Some ideomatics are just different. So when tackling something, you naturally do it like you’ve been doing it before in other language(s). In the beginning it just doesn’t occur to you, that something might be done (entirely) differently in this new language. It takes time to pick up and sometimes even more to wrap your head around it. Open-mindedness certainly also helps, I found. The more you’ve really worked with different languages, the more your little knowledge base grows. Hence, you know that things can be solved in lots of different ways. And that will basically bring you awareness, that you might want to look out for the specific procedures of doing something in that other language you’re using.