If this works as expect, I love it. I'm assuming the user doesn't need to manually configure the containers etc; it sounds like from the Readme it's low-frictio

If this works as expect, I love it. I'm assuming the user doesn't need to manually configure the containers etc; it sounds like from the Readme it's low-friction. From a performance and disk space perspective, I'm not thrilled about containers. I think their existence here and in general cuts to a deeper concern we can fix. Here's what I'd like to see for GPOS software in general. (Win, Linux, Mac, any new ones we get) Minimal or no ABI barriers. You compile software for a given CPU architecture, and it just works on all suitable operating systems. No barriers; no friction. There are some OS specific things people use like file systems, threads, and allocators, but these are usually somewhat general, and are abstracted over by the programming language's standard libraries. This is a worthwhile goal, and technically is feasible. Within Windows, this generally works pretty well; I think a reasonable goal is to get this working within Linux as a whole. Then cross Win/Linux, and maybe even Mac. OSs should be making our lives easier; not putting up barriers. Especially with the Linux free/OSS mindset. I wish UX and Compatibility were part of the ethos too; I think it's relevant.