• Post Reply Bookmark Topic Watch Topic
  • New Topic

Leaky abstraction  RSS feed

 
Tushar Goel
Ranch Hand
Posts: 934
4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I was reading an article http://www.joelonsoftware.com/articles/LeakyAbstractions.html on Leaky abstraction which explains it using an example
of TCP/IP. It basically tells us that a perfectly abstract design also have leakage as high level doesn't know all the condition in which leak can happen.
Example: For TCP/IP example, wire can be cut by someone so that package will be lost and higher level doesn't about it.

But what i don't understand is what actually author wanted to communicated. Is he wanted us to inform that whatever best design we can have, leakage
can happen or he wanted to let us know to find the same we need to check deep(low level) to find the leakage?

Could you please tell us what is the motive?
 
Campbell Ritchie
Marshal
Posts: 56599
172
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It says quite clearly in the article you quoted
Joel Spolsky wrote:All non-trivial abstractions, to some degree, are leaky.

Abstractions fail. Sometimes a little, sometimes a lot. There's leakage. Things go wrong.
Does that answer your question?
 
Tushar Goel
Ranch Hand
Posts: 934
4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So he only wanted us to know that we have leakage in all the important abstraction...
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!