Yup, it's good of DAZ to provide a good piece of modern software and all that. But interface design doesn't have anything to do with whether new hardware is supported or not. If you're happy to learn a new interface for every piece of software that comes out, then that's fine, but personally I prefer to spend the extra time using the features of the package and it's helpful if everything is where I expect it to be. One of the fundamental tenets of UI design states that there should be as little switching between mouse and keyboard as possible so as to create more fluid workflow. Now if you extend that idea to software interface paradigms, then I would think it counter-intuitive to have to remember the subtle nuances of each interface for a spread of programs that I might use in the creation of one project. This is the situation that existed in DOS days and was generally considered horrible. I don't really see where the past or present comes into it. Poser's underlying code might be showing it's age but, again, that has nothing to do with the interface. I've seen reviews bashing Lightwave for it's interface, which doesn't have any relevence to it's abilities as a program. It used to be thought that the way forward was to harmonize differing applications through the use of a common UI. I believe that to be still true and I've seen nothing that Poser or DAZ Studio requires that isn't already provided for by the controls and dialogues present in Window's own toolset. By the way, I should point out that I'm not necessarily trying to preach that Windows is great or anything; I think it's no better or worse than any other environment. But I only had to learn how to use it once and I then knew how to get around in many, many packages thereafter. You actually LIKE the interfaces used by Poser and Bryce, Ghostofmacbeth? Well, I suppose someone has to! ;)