I&#x27;m a bit skittish about tools like this.<p>We started using one for C# a while back, and discovered a couple key problems with it. First and foremost, sometimes its edits were not safe to do in the context - either that commented code really was important to keep around for some specific reason (e.g., it serves an explanatory purpose), or sometimes the changes were not truly behavior-neutral and would therefore introduce subtle bugs.<p>In light of that, I&#x27;m moving away from thinking that using tools like this as a sort of spray-on tan for cleaning up code is wise. I&#x27;ve started leaning toward the following approach: First, let sleeping dogs lie. Old messy code is like asbestos; it&#x27;s most dangerous when you disturb it. Second, if you&#x27;re going to have to work on the code anyway then that&#x27;s an appropriate time to clean it up. Even so, proceed with caution: Make sure you understand the code and it&#x27;s got good test coverage so you can visually and empirically verify that the cleanup isn&#x27;t doing any damage.