Maybe I'm just too set in my ways - but nothing in this article looks like a solution to anything remotely relevant to most software development. Difficulty in

Maybe I'm just too set in my ways - but nothing in this article looks like a solution to anything remotely relevant to most software development. Difficulty in updating software isn't a new problem - but we already have much, much better solutions than this. I don't think there's anything wrong with changing existing code - and if changing existing code is causing you so much pain that you're led down this route, then you probably have bigger issues. Maybe this methodology just isn't for me - but I really don't see how this improves anything from a development perspective. I only care about the current state of the code - and if I need to care about the previous state of the code, then I just check the history. The idea of having to understand the entire history of a codebase just to grok the current state seems insane.