From APIDesign
(Difference between revisions)
|
|
| Line 1: |
Line 1: |
| - | This section is good, and reminiscent of (symmetric to?) your section at the beginning of Part 3, "An API Must ...".
| + | Send you old APIs to black hole smoothly with help of this chapter. |
| - | | + | |
| - | One thing I would recommend: an additional section of this chapter about communicating and distributing one's API. In my experience, a number of people have developed APIs which may be either good or bad, but which I have little chance of knowing, because it's presented so badly as to discourage me from investigating further, thereby rendering all of the work that went into the API somewhat useless. I know this isn't purely a software thing, but I think communicating an API clearly - what it does, what its limitations are, how it works!!! - is very important.
| + | |
| - | | + | |
| - | --[[User:Dmkoelle|Dmkoelle]] 02:56, 23 April 2008 (UTC)
| + | |
| - | | + | |
| - | "... but also whole packages like java.beans.beancontext that are there without any further reason." Why? This package has not been deprecated AFAIK and it may still be quite useful to some.
| + | |
| - | | + | |
| - | --[[User:TomWheeler|TomWheeler]] Wed Apr 23 20:38:48 CDT 2008
| + | |
| - | | + | |
| - | what is "paste jewelry"?
| + | |
| - | | + | |
| - | --[[User:Richunger|Richunger]] 05:23, 26 April 2008 (UTC)
| + | |
Revision as of 06:36, 14 June 2008
Send you old APIs to black hole smoothly with help of this chapter.
Follow
