I guess I agree. I have had to debug .NET code through plugins like the Deblector before, and it's not fun. Thankfully, I don't have a job that often requires me to single-step .NET.
All I want to point out is, the capability of turning bytecode into high-level source code isn't new. It's something the free version of Reflector has done beautifully for years. If you work in higher-level languages (like Java, C#, PHP or Python), you should probably be aware that your source code is out there, even if you publish only bytecode.
I'm never going to forget the shock on the faces of my co-workers when I told them that by using reflection and looking at the bytecode/MSIL you can get pretty much anything that's in the executable. "But why does .NET allow you to access private fields? Isn't that a security hole in .NET?" They apparently based the security of their application on the assumption that an attacker cannot read private fields of their objects. Man, do I need to find another job.
Re:.NET Reflector Pro is awesome
by Quarrelsome on Tuesday January 12, 2010 @12:21PM
(#1047966)
I'm going to use it to trace down those first chance exceptions that fire in oh so many 3rd party frameworks (and .NET itself).
I hate those things and want to see if they could have avoided them. :)
To put it another way, I think you're missing the forest for the trees, i.e. the benefits for the features, in a way that so many engineers do. The crucial feature isn't new. The benefit of this application is huge, and improves the usefulness of plain decompilation (+ analysis etc.) by about 3x IMO.