|
|
|
| Authored by: Anonymous on Tuesday, April 17 2012 @ 07:34 PM EDT |
Long term API stability is also present in much of UNIX's standard library set.
I have code that is decades old that still compiles and runs. It even passes
all of the unit tests. It was originally written on a System V UNIX and porting
to Linux was just a recompile. Edits to meet Strict ANSI compliance were the
hardest part, and I did most of them with perl scripts.
X-Windows system is also another area where long term availability of APIs is
present. It is real nice when your vendor isn't pulling the rug out from under
you every OS release.[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Tuesday, April 17 2012 @ 09:02 PM EDT |
Java programs written to java.awt will still run
More recent java programs will use java.swing
Java has deprecated many parts of the API, so, like perl some programs may not
run, but most will.
There is only the current API, or even (if you wish to split hairs, the
currently installed API)
Design of your application as to which parts of an APIs you choose to use is a
separate question from implementing APIS.
"Good" in the context of an API is relative. Tomorrow, like java.awt
it will be less than Good.
[ Reply to This | Parent | # ]
|
|
|
|
|
