hypervisor VS CppCoreGuidelines

So I'm working on making a hypervisor for my school. I've looked into the vendors like Proxmox, Vmware, etc. and I haven't found one that will let me make my own GUI. I have looked at pages like this https://rayanfam.com/topics/hypervisor-from-scratch-part-1/ or projects like Bareflank here https://github.com/Bareflank/hypervisor and they don't QUITE seem like what I am looking for, unless I'm just blind. I just want to have a hypervisor that can spin up oh so many virtual machine instances of Windows 10 and accessible in a browser. I want to have the freedom to make my own GUI so I can tailor it to my school's website. The idea is it's just something freshman can screw around with and have the option of spinning up a few VM instances as they please, while keeping in mind a very simple GUI a freshman could figure out. I'm not too concerned with hardware limitations, I just want to see if this is even possible, and if I have to deal with crap hardware/software that can only spin up 2 instances or something, so be it. I understand that I very well may be looking for a unicorn in that I will have to either use a vendor and accept their GUI or go through a monolith of assembly code to build my own, but if anyone has any suggestions or github links to help me do this in a reasonable amount of time it would be much appreciated.

You need to talk to Bjarne and Herb...

"C++ Core Guidelines" - https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

In addition to the other comments -

TypeScript deliberately takes a "good enough" approach to improving JavaScript, instead of designing an ideal but incompatible approach. For example, its handling of [function parameter bivariance](https://www.typescriptlang.org/docs/handbook/type-compatibil...) is unsound but works much better with the existing JavaScript ecosystem. By contrast, a more academic functional programming language would guarantee a sound type system but would be a huge shift from JavaScript.

By analogy, Herb Sutter is arguing that something like the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines), with tooling help in this new Cpp2 syntax, can bring real improvements to safety. Something like Rust's borrow checker would bring much stricter guarantees, backed by academic research and careful design, but would be incompatible and a huge adjustment.

https://www.youtube.com/watch?v=2olsGf6JIkU

Take a look at Effective Modern c++ by Scott Meyers and the ISO c++ core guidelines. These resources are great for learning how to write better, more modern C++. I don't think it would be hard to grasp if you're already familiar with the language, just make sure to actually write some code which makes use of this stuff, otherwise it's easy to forget.

Look to the C++ Core Guidelines. It's not perfect, it has some flaws, including some sabotaging advice apparently adopted for political reasons. But at least it has some C++ authorities (Bjarne and Herb) as authors.