[Infrastructures] Coda, to do or not to do?

[Ivan Popov]

Hello Steve,

On Thu, Mar 17, 2005 at 01:32:42PM +1300, Steve Wray wrote:
> It turned out that if the client tries to access a file which is larger 
> than the client side cache, the server would crash. Badly.

are you sure you recall it correctly?

> When I raised this on the coda mailing list (its probably in the 
> archives...) it appeared that this was a design 'feature' and the 
> comments I recieved from the coda development team was that it would be 
> almost impossible to fix this behavior.

I guess you might confuse that with a limitation on the number of files
in a single directory. There was once a bug (properly fixed) which made
the server crach. The limitation is still there, but not at all in the way
you describe.

It would clean away a possible confusion, if you supply a reference
to the relevant thread.

> Coda is also (still) *full* of performance-draining debugging code 
> which, again from comments made by people on the coda development team, 
> would be *exremely* hard to remove from the code base. The whole thing 
> would need refactoring.

> This was a few years ago. Perhaps its improved? But I certainly wouldn't 
> trust data to it.

I appreciate your interest to Coda, even if you did not like it then.

On the other side, I have been on the Coda list for many years
and I feel that the way you tell about your experiences may be misleading,
especially a long time later.

Coda does not cope (by design or by implementation) with some scenarios -
like shared video editing or huge flat directories.

Coda is working nicely for distributing software or accessing one's own files
both at work and at home, as well as sharing files across the globe.

Best regards,
--
Ivan