bmcgee84

Nothing wrong with the workflow you described, done much the same in the past myself.

Yup

Thanks. It's a pattern I saw in https://github.com/LMAX-Exchange/disruptor.

I'm new to Go, still finding my way with the idioms. Since there's nothing internal and this is just a small library I can see how it's simpler to flatten the directory structure, which also seems to be how other libraries do it.

Certainly there will be overhead, and I can see how it can quickly mount up. Each person will have a different idea of where the tipping point is in terms of that overhead. For me personally, what was described is not that onerous.

30 is a bit of an exaggeration don't you think? I counted 13 tools, 9 of which share (or can share) a common login (Google). This is far from as onerous as you're making it out to be.

I've been using Google paid services for almost 4 years now, I've yet to experience any issues. That being said I'm not saying I never will experience such problems, but on balance I would argue the risk/benefit for a small business is much more in it's favour.