DEV Community


Discussion on: The Problem with Interfaces, and how Go Fixed it

jervine791 profile image
john ervine

The word awesome is over used. Your main selling point is a developer doesnt need an in depth knowledge of the code base there working on. If developers are forced to work with an interface they will simply implement it. I would not want implementation of my interfaces spread throughout my code base. I think its a code smell. I want to know what my code implements.

dean profile image
Dean Bassett Author

Really the main point I was trying to make is that code from other libraries can be easily used in code you make. If you bring in a library which supplies an HttpRequest, and you have an interface called Requester which has a Request() method, as long as HttpRequest has the Request() method, it conforms to the Requester interface and can be used where you'd want it to be used.