Do what it takes to get them to a doctor and let them handle it. For example: "I want to support you, but I am no expert. Let’s see a nutrition specialist to see what the best course of action is. Personally, I think you are not too fat, but if there is something you want to change, let’s do it right.

That’s the beauty. Given that there is no goal, you are able to define your own.

I have set up a good hand full of dual booted Windows/ Linux machines. Never had any major issues. However, I also noticed that I only use Linux except for games and that’s slowly changing, too, so I would suggest trying the dual boot if it makes you more comfortable to realize yourself that you don’t need it.

Yes, it is absolutely valid that you decided to commercialise your project and keeping parts or all of the code closed. As I work in the public sector and we are encouraged to use open source and write open source software, my knowledge regarding closed software solutions is thin. Is there a “standard way” how closed software is able to guarantee private key safety? I could imagine solutions where there is a separate handler that is open source so that one can verify that only specific information is passed into the closed software area, but this doesn’t sound feasible when talking about full terminal support within the closed software.

Again, there is nothing wrong with going commercial! I am sure I will release closed software (side projects), too, at some point.

Giving it a quick scan, it does look interesting. I am not sure whether I will try it as I don’t see the need to visualise beyond what I can do with a shell and the openstack dashboard, but there can definitely be use cases for it.

Not being FOSS is the deal-breaker though. Not sure if I am too much of a sceptic but I prefer open source when having software that accesses my private key/servers.