data, objects, documents, code, etc

Patrick Logan (patrickl@servio.gemstone.com)
Tue, 17 Feb 98 12:51 PST

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: rohit@godzilla.ICS.uci.edu: "[BITS] Week7 readings : Modularity in standards and markets"
Previous message: Gregory Alan Bolcer: "Re: My music notes, Feb 4, 1998."
In reply to: glen e. p. ropella: "data, objects, documents, code, etc"

Whether one is distinguishing between data and code by saying
that "Code is expensive and data is ephemeral" or "... as platform
half-lives collaps, externalized data lasts longer and longer by
comparison", it's still a distinction between code and data.
And this distinction is false.

Ideally, I agree. The lack of a distinction is the
asymptote. Right now today, the distinction is a reality that has many
context dependent issues. Today's "state vs. behavior" debate is
a different debate from what another system may be like. There are
good reasons to be involved in both debates.

In other words, we are going to have to cut things much much
finer than "object", "data", or "code" in order to get at anything
useful, here.

It's not easy leaving Plato behind. What does "Maturana-gol" look
like, after all? ;^/

-- 
Patrick Logan                 mailto:patrickl@gemstone.com
Voice 503-533-3365            Fax   503-629-8556
Gemstone Systems, Inc         http://www.gemstone.com

Next message: rohit@godzilla.ICS.uci.edu: "[BITS] Week7 readings : Modularity in standards and markets"
Previous message: Gregory Alan Bolcer: "Re: My music notes, Feb 4, 1998."
In reply to: glen e. p. ropella: "data, objects, documents, code, etc"