Skip to content

Comment on Applying The Clean Architecture to Go applications

Comments

Only skimmed, but this seems like a very verbose way to say that you should get your dependencies right.

But Go has the most important part almost automatically, because it doesn't allow cyclic dependencies. If package A depends on package B (directly or indirectly), B cannot depend on A. So when reorganizing, you have to decide which package is higher in the stack.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.