On Oct 1, 2007 6:16 AM, Ben Collins-Sussman <sussman@red-bean.com> wrote:
> I have to admit, I thought this would be the case too. Then I came to
> google, where we use perforce every day, and after two years it really
> doesn't seems like a big deal at all. It's not noticeable. I suspect
> other svn-committers-who-are-googlers would agree with me.
I think it's perhaps more that you got used to the delays and workflow
intrusion.
At Google when I was there, p4 edit took ages - into the order of
minutes - to permit writeability for a single file - it's certainly
not a unnoticable operation. Admittedly, it may have been because of
the way p4 was configured at remote offices. Though, I don't recall
'p4 edit' being particularly fast in Mountain View either. I do
recall that 'p4 opened' was *way* *way* slower than 'p4 edit' - that
was even more annoying as it was impossible to quickly discover what
files you had opened for edit! Our team would schedule coffee breaks
and/or Nerf fights around p4 commands. =P
Of course, I would bet our implementation of 'svn edit' would be
faster than Perforce as we wouldn't have to advise a central server
when we want to edit a single file. So, the performance aspect should
be mooted.
Setting aside the performance aspect, based on my own experiences with
Perforce, I'll strongly disagree that *mandatory* 'svn edit' is a
feature we would *require* everyone to follow. The required workflow
change is simply not something I'd want to impose on everyone.
Optionally? Sure - if you have a large enough working copy and/or you
don't mind altering your own workflow. But, I think there are many
many users who would find 'svn edit' mandatory a huge turn-off -
especially given where we've come from.
I don't want SVN to be my nanny. I'm personally happy to trade a bit
of performance for not having to run 'svn edit' before modifying any
file in the WC. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 1 18:26:17 2007