encapsulation and abstraction are related .. he meant that that the details of how it's done is encapsulated and not accessible to the consumer of the api .. he can only access the exposed methods and that's important if they later decided to change anything in the implementation your code will not be affected and doesn't even know about it ... and in the end is abstraction too
@16:00 -- But aren't the functions passed to higher order functions objects too? If a lambda is the name for an object of an anonymous inner class that implements a "single abstract method" interface, then it is obviously an object. Isn't it? But we tend to call it a "function" coz the function is the predominant component of the lambda content Please comment? (even though I know there is 0.1% probability for you to see this comment) :)
