Scott Jones’ Weblog

I toned down the last paragraph of this Juice article last week for posting on the company site. But I can’t help myself. Here’s the original edit:

The great part for SVS development is that we didn’t have to write any of this stuff. All the needed info was just there in Windows, waiting for SVS to come along and use it to make magic. This is one example of what I mean when I say that SVS extends the plumbing that is inherent in native Windows. MS put the process tracking system in place for a lot of reasons, but it’s core to SVS being able to do what it does. It makes redirection and prioritization — and the resultant normal visibility of virtualized apps — possible. It’s one of the reasons why the lead engineer who invented SVS, Randy Cook, knew that we didn’t need to build a new, alternate execution environment like other app virtualization vendors have. They didn’t need to build a proprietary execution environment, either, actually, but they did anyway. And you see the results. Guess Randy just understands Windows architecture better.

Filed under: SVS and