"Persistent Compatibility: allowing host and application to evolve separately. Changes in the host don't break applications."
"A library OS is an operating system refactored to run as a set of libraries within the context of an application.
While Drawbridge can run many possible library OSes..."
This implies to me at least that the app and the "OS" the application sees is a complete isolation from the host OS.
But I might be misinterpreting things here, the video seems to go into a better explanation
http://channel9.msdn.com/Shows/Going+Deep/Drawbridge-An-Expe...
Strategically this could allow Microsoft to drop lots of backwards compatibility cruft in their mainstream host OS and vastly reduce development cost and complexity.
See my previous comment here https://news.ycombinator.com/item?id=8245682
"Persistent Compatibility: allowing host and application to evolve separately. Changes in the host don't break applications."
"A library OS is an operating system refactored to run as a set of libraries within the context of an application.
While Drawbridge can run many possible library OSes..."
This implies to me at least that the app and the "OS" the application sees is a complete isolation from the host OS.
But I might be misinterpreting things here, the video seems to go into a better explanation
http://channel9.msdn.com/Shows/Going+Deep/Drawbridge-An-Expe...
Strategically this could allow Microsoft to drop lots of backwards compatibility cruft in their mainstream host OS and vastly reduce development cost and complexity.
See my previous comment here https://news.ycombinator.com/item?id=8245682