News for hackers. Stuff that matters.
Re:From Java to Go, and Back Again (2016) by hocuspocus on Saturday June 23, 2018 @03:39PM (#17383005)
> public interfaces help to make dependencies clear and honest.

Again, moot point if there's only one implementation.

> If the implementation doesn't provide more methods than the interface (a transparent class in GoF terminology) you should not name it.

> In Java, the implementation is usually created inside a static method (a static factory) of the interface as a lambda or an anonymous class.

And how's that not needlessly convoluted and ugly? You're illustrating guitarbill's point about applying design patterns blindly.

There are no comments on this comment yet.