Pascal and Arail, I think it is a worthwhile goal, both as an individual user and for Rhino 6, to make running with Always Record History the default behavior. It requires an adaption in thinking, IE, instead of moving an extrusion move the creation curve and let the extrusion follow, but the results make for powerful updating of the model. Selectively purging history is part of that thinking. One of the best features of Rhino history is that it is saved in the file, and will carry forward with SaveAs. Last week I opened an old file, point-edited a single curve, which updated 80 curves that had been created by Orient On Surface with copy option, which updated 40 One Rail Sweeps using the adjusted curves as profile curves. The key to making this possible was knowing that the next step, capping the sweeps, would break the history, so I had copied them and capped the copies, leaving the originals intact for future modifications. As Rhino continues to add history enabling to more commands (like Cap, and–this is really big I know–Fillet), it will be possible to carry these types of update even further. Blocks themselves are a kind of history, so if you’re used to updating blocks the step to recording all history is natural.