'. '

Leaky abstractions

From APIDesign

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
-
When creating an [[API]] one is creating a facade, an abstractions over the internals of the [[API]]'s implementation. Often the characteristics of the implementations are visible through the [[API]]. This is common source of [[wikipedia::Leaky abstraction|software bugs]].
+
When creating an [[API]] one is creating a facade, an abstractions over the internals of the [[API]]'s implementation. Often the characteristics of the implementations are visible through the [[API]]. There is some controversy on [[wikipedia::Leaky abstraction|wikipedia]] whether this is good or bad and even whether the original [http://www.joelonsoftware.com/articles/LeakyAbstractions.html Spolsky's article] is properly understood. Let me add few comments to this debate from the perspective of [[cluelessness|selective cluelessness]].
-
Leakages of this kind are not restricted just to the world of [[API]]. After writing [[TheAPIBook]] I also noticed that I made my own [[LeakingCulturalContext|cultural context leak]] which created an unwanted confusion.
+
TBD
 +
 
 +
Leakages of this kind are not restricted just to the world of [[API]]. After writing [[TheAPIBook]] I also noticed that I made my own [[LeakingCulturalContext|cultural context leak]] which created an unwanted confusion and led one of [[TheAPIBook]]'s reviewers to reject to publish its review.

Revision as of 08:32, 31 October 2009

When creating an API one is creating a facade, an abstractions over the internals of the API's implementation. Often the characteristics of the implementations are visible through the API. There is some controversy on wikipedia whether this is good or bad and even whether the original Spolsky's article is properly understood. Let me add few comments to this debate from the perspective of selective cluelessness.

TBD

Leakages of this kind are not restricted just to the world of API. After writing TheAPIBook I also noticed that I made my own cultural context leak which created an unwanted confusion and led one of TheAPIBook's reviewers to reject to publish its review.

Personal tools
buy