LinWin Experiment 1 : Virtualized WSL Launcher

In this blog, I am going to pen down my first experiment with Windows Subsystem for Linux where I virtualized WSL's launcher component. I'll start with summarizing my WSL learning (with links to Microsoft's site) and then take you through the setup and how I ended up virtualizing WSL launcher. I am yet to analyse it fully, so I'll be posting followup blogs as I move on with my experiments. I would really like to get feedback from those who experimented with WSL earlier. I've used tools like APIMonitor, WinDbg, ProcessHacker and Cloudhouse's Virtualization engine while trying these experiments.

What's Next.. "One App"?

Yeah, I hear you! That’s a confusing name “One App”, what would that mean? Sorry I didn’t find a better title (after reading this blog, you might be able to suggest a better one). A disclaimer first, this is a debatable blog, as I am questioning the very basis of the software industry. Different people might have different opinions on this and I am open to differing views and ideas.

My Journey towards invention of Compound Application Virtualization

For the first time in the history of application virtualization, competitive virtualization technologies are combined together to form a superior solution, overcoming the limitations of each of the individual virtualization engines. This opens up a whole new world for innovative next generation Hybrid Virtualization Solutions. I like calling it “Compound Application Virtualization” (a name my colleague Rikard Ottosson suggested).