News for hackers. Stuff that matters.
Re:Java Doesn't Need to Be So Bad by VladRussian on Thursday December 08, 2011 @09:22PM (#3332222)
> If/when you have multiple concrete objects which share the same interface, it's trivial there to switch references from the concrete type to that of the Interface

you're a lucky person that it has been trivial for you, your teammates and all the known and unknown clients of your code and components. I can only envy your experience.

Re:Java Doesn't Need to Be So Bad by timclark on Friday December 09, 2011 @04:01AM (#3333121)
Lots of Java development is carried out for internal business applications and like it or not they would typically be integrated with third parties using something like SOAP or a shared database. So in this type of application the choice of a concrete class over an interface probably has little impact on the known or unknown clients of your code.

However, as you point out, if you are presenting a Java API to your known and unknown clients you had better think carefully about which abstractions you are going to expose and interfaces are probably going to be very helpful.