Hi,
I'd like more infos/discussions about CoreObject...
If I understand well, it's intended to be a Data store, where
applications could store their datas; but the datas are structured
(~objects) [1]. And this datastore is/will be written in C, and thus
potentially accessible from anything. Then we'll have an Objective-C
framework on top of that. Then possibly the datastore will manage for
us the versioning, and possibly higher-level frameworks will be in
charge of object persistency using this datastore, and the datastore
will also be indexed using LuceneKit. Am I right here ?
If so, .. I must admit I don't see what's so different about that
concept compared to the idea I was pushing of a "local" data store
indexed, "separated" from the rest of the filesystem ... so what did
I miss ?
But then of course if I'm right, I really think it's a good idea,
particularly in light of my recent readings about NewtonOS : having
data easily accessible from any other programs is a great thing,
because it will help creating synergy among the programs !
If you think that way, what are the problems of an "application
oriented" environment ? well, I can see two major problems:
- the data is "proprietary"
- code reuse is low
If we use a common data store, then we get rid of the first problem,
and furthermore we easily add great benefits, mainly, versioning and
indexing.
Thoughts, remarks ?
[1] could it be interesting to really store *objects*, that is, in
addition to define a structure, we can also store behavior ?
--
Nicolas Roard
"Any sufficiently advanced technology is indistinguishable from magic."
-Arthur C. Clarke
