openvmm

> OpenVMM split up its docs and there isn't much in the actual README, but a few seconds investigation led me to https://github.com/microsoft/openvmm/blob/main/Guide/src/dev... , for example. this is a reason to reconsider my statement why? > Come on, this is not even a good strawman. It's not a straw man at all. It's my opinion. > It's very easy to find out the language of you want to know, and it's possible to inform without evangelism. Indeed, but nothing makes it more straight forward than the language being mentioned in the HN News title

> I doubt that a GitHub README is used for language evangelism. Perhaps you should reconsider this. OpenVMM split up its docs and there isn't much in the actual README, but a few seconds investigation led me to https://github.com/microsoft/openvmm/blob/main/Guide/src/dev... , for example. > Also, I don't find it annoying, but helpful, because I care - amongst other things - about the language of open source software projects. Come on, this is not even a good strawman. It's very easy to find out the language of you want to know, and it's possible to inform without evangelism.

Note this “disclaimer” in the guide: > In recent years, development efforts in the OpenVMM project have primarily focused on OpenHCL (AKA: OpenVMM as a paravisor). > As a result, not a lot of "polish" has gone into making the experience of running OpenVMM in traditional host contexts particularly "pleasant". > This lack of polish manifests in several ways, including but not limited to: […] > • No API or feature-set stability guarantees whatsoever. https://github.com/microsoft/openvmm/blob/main/Guide/src/use...