2 ms·
Maybe "hiding what a process is" is not that good an analogy for "hiding what a modern VCS is under the covers", after all, users know to use task killers on ju
by cryptonector 12y ago
Maybe "hiding what a process is" is not that good an analogy for "hiding what a modern VCS is under the covers", after all, users know to use task killers on just about... every OS. Or maybe that is a good analogy: users need to know how to kill runaway/non-responsive apps. Calling processes "tasks" or "apps", or something that will mean more to users is a very good idea, but you can't entirely hide the concept from them. (For many elderly people even that is too much.)
Here's what I think might help users: a) better diff/merge tools (like github's new image diffs), b) better integration with VCSes in every application that produces content (e.g., Adobe Photoshop), c) better visualization of the history tree.
For (c) I'm thinking of a D3-style graph, with recent branches taking prominence (whether named or not). Mouse around the graph to pick out branches, mouse over commits/heads to get a blurb (branch/tag name, last commit metadata). Something that feels alive and dynamic. Not these static, boring branching graphs we've all seen before that look like SVG renderings of ASCII art graphs taken from manpages. Static graphs become difficult to display and use when the number of branches increases past a handful.