|
Authored by: stegu on Tuesday, April 17 2012 @ 06:24 PM EDT |
I guess it depends on what the API is about.
My experience with graphics, and with Java2D
in particular, is the exact opposite of yours.
The Java2D API design is largely a carbon copy
of PostScript, with the same imaging model and
largely the same graphics primitives. It aims
at doing more or less the same things as
PostScript or SVG does, in much the same manner,
only with a Java class-based syntax instead of
a postfix stack-oriented command language
(PostScript) or an XML schema (SVG).
The implementation of Java2D, on the other
hand, is responsible for turning abstract
drawing commands into pixels on a display,
and that requires large amounts of highly
non-trivial code that I would reckon takes
orders of magnitude more time and expertise
to write than the API specification.
[ Reply to This | Parent | # ]
|
|
|
|
|