2 ms·
From TFA it sounds like Envy was version control that people didn't find skull-crushingly painful to use, which establishes it as pretty different from CVS or C
by smacktoward 9y ago
From TFA it sounds like Envy was version control that people didn't find skull-crushingly painful to use, which establishes it as pretty different from CVS or ClearCase.
- eesmith 9y agoHeh-heh. After working with RCS, CVS, SCCS, SVN, and Bazaar, I find Mercurial to be a good fit for my model of how to work, while using git drives me batty. Perhaps my skull has been crushed already. :) FWIW, I and others in my group used CVS for years, after migrating from RCS. We didn't find that difficult. I didn't get a sense from the article that the people involved found RCS, ClearCase, or CVS that hard to use, only that Envy was a good fit for how they used Smalltalk.
- igouy 9y agoENVY fit how Smalltalkers used Smalltalk. Accepting a code change locally, in the usual way, created a new edition in the database. Once editions were versioned and released they would become visible to other developers, and loadable by-default.