Is Yukon for software developers or system engineers?

I ask this because I suddenly realized I never considered this question before. It seems like there are two types of tools we could build but the system engineer actor seems very different from the software developer. The former is using the tool like a scope; monitoring, tuning, and validating. The software engineer is using the tool like a debugger; testing, modifying, simulating, and analyzing. A systems tool would be much simpler, lighter-weight, and user friendly. A software tool would be more powerful, invasive, and data rich.

Yeah. I expect that Yukon is going to be both, I think that the needs of a software engineer are a superset of those of the systems integrator. I am going to put my thoughts together soon and post them in GUI Tool – Next Generation – I think I have a very radical idea.