[Pygui] Python 3 Plans

[Greg Ewing]

Andrew McNabb wrote:

> Since versioned file
> systems do everything automatically, it's very difficult to make sense
> of concepts like branching, merging and commit messages, which are
> critical for large projects.

You wouldn't want your whole disk to just be one big
versioned file system. What I have in mind would be
more like mounting a disk image on MacOSX. Each
repository would be a volume of its own, and there
would be an interface for doing all the VCS type
stuff like branching and merging.

> I didn't know that BBEdit uses resource forks; that's very interesting.

The version I'm using is rather old, so I'm not
sure whether current versions still do. I ought to
get hold of TextWrangler at some point and find out.

> Does BBEdit work if it's used with a UFS filesystem?  I'm pretty sure
> that UFS can't deal with resource forks.  What does it do if a file is
> stored on a FAT filesystem?

MacOSX has alternative ways of storing its metadata
on non-HFS file systems, e.g. on UFS I think it creates
._filename files, and on FAT it uses a directory called
something like __MACOSX.

> Resource forks certainly have benefits on standalone machines, but I'd
> rather give up resource forks than network communication. :)

Same here, but it's disappointing to be forced to choose
between the two.

> I think its biggest weakness is the size
> of the community behind it.  The only reason that I've made such a big
> deal about the VCS issue is that I think this is a small thing that
> could make a big difference.

You may be right. I'll give the matter some serious
thought.

-- 
Greg