On 12 Jan 2004, at 16:40, Berin Loritsch wrote:


So your point is well taken, and is theorhetically correct. But don't be
deceived, there is energy expended to convert from ad hoc cocoon systems to
one based on blocks.

Very very true. This is understood and taken into consideration. At the same time, one requirement is that you should be able to use Cocoon 2.2 even if you don't want to use blocks nor know what they are for.


I want users to not even feel the transition and find themselves with solutions when they hit the problem.

At this point, the energy taken to move will not be felt like wasted, but be felt like a "state transition", might increase disorder for a while, but moves things to another level.

There will be energy lost in the conversion, no matter
how careful we are to move from liquid to solid.

Yes, we are all aware of this, but we work to minimize this.


There will also be energy lost
if we had to switch back.

Again, very very true.... but as we showed with your work on Fortress, if there is 20% job done and we can throw away, we would rather keep adding the 80% remaining if this makes sense from an evolutionary perspective.


Though not nearly so much as if blocks were written
with backwards compatibility thrown out the window.

Yes, that's my point exactly.


I'm very glad that we resonate on these concepts.

--
Stefano.



Reply via email to