Sun rejects orthogonal persistence for Java

[shapj@us.ibm.com]

> The normal argument is that it saves the programmer
>from writing redundant and error-prone manual saving logic.
>Why write code to save state when you've already written
>code to represent that state in memory?

The normal argument is mistaken.  Data does not live in a vacuum.  If we ignore
persistence, we still must address the problem of data interchange: a bitmap
must have some relatively universal representation understood by all graphics
editors.  Thus, persistence does not eliminate the need for serialization code.

Jonathan S. Shapiro, Ph. D.
IBM T.J. Watson Research Center
Email: shapj@us.ibm.com
Phone: +1 914 784 7085  (Tieline: 863)
Fax: +1 914 784 7595