3 ms·
On that same note I've often wondered how useful it would be if our IDEs actually recorded our keystrokes as we developed code. The problem with commits is that
by hackinthebochs 13y ago
On that same note I've often wondered how useful it would be if our IDEs actually recorded our keystrokes as we developed code. The problem with commits is that we only see the end result. There is usually a process of evolution of code, and through this evolution we can fully understand the end result. So much information about a codebase is lost because we only see the end result.
Git and Mercurial are steps in the right direction here. You see groups of changes as one unit, and the philosophy of these systems is one of frequent commits. But what if we went even further and could see code evolve as its being typed?