
[in the future, Raymond, can you send these to python-dev? I don't think python-checkins is the right place to have over-arching discussions about stuff] On Sat, Jan 24, 2009 at 15:47, Raymond Hettinger <python@rcn.com> wrote:
You're added space/time measurements to the PEP. I think you ought to add another more subjective measurement for each system. How long did it take you to learn the new commands and ways of working with the system. How long did it take to get it configured and working on your system? What would be the impact on your life as a developer if you had to switchover?
Talking about the Python language itself, we often make the point that developer time is far more important than saving a few clock cycles on a computer. The real impact of a switchover is the learning curve and configuration time multiplied by the number of developers.
My impressions are not done yet. If you look at what I checked in earlier today you will notice I discuss how long it took to figure stuff out, etc. I am keeping it simple for now but I will discuss subjective things in more detail at a larger context when I come closer to reaching a conclusion.
Also, how many developers or casual contributors will we lose because they simply aren't willing to bear the transition costs?
That's an unmeasurable number short of seeing how large of an outcry there is against something. And since I have not even made a case for one DVCS over another it isn't worth worrying about this number quite yet. -Brett