By mswatcher
via codethinked.com
Published: Jun 12 2009 / 21:38
Back when Dinosaurs ruled the earth, developers had these things called API references. They were physical books (made of paper) which contained thousands upon thousands of pages of nothing but documentation for APIs. If you wanted to do something, and you didn't know how, you either asked the wise old developer that was working with you or you looked up the answer in the API reference.
Comments
overtheline.myopenid.com replied ago:
Reading the manual against your will by googling is not a development tool. But it is helpful in alot of cases give our assumed lazyness.
As long as you accept that 80% of what you google on the web is not on point or wrong. But at least its there.
In high school if the calculator you used in physics class was as sketchy, you would flush it down the toilet.
So whatever. I was hoping you would talk about APIs themselves. They are actual development tools and are largely dying.
Gene Gotimer replied ago:
The idea of the article was OK. Not great, but OK. The writing was almost unintelligible, and the downsides are not mentioned at all (many wrong answers, most of the time the solutions don't explain drawbacks or limitations, etc.).
Voters For This Link (12)
Voters Against This Link (2)