There seems to be some confusion about what exactly “web based ground control” is. It is already platform independent as it turns the UI in to a web service rather than a local application. So you can access it with any modern browser.
On the backend, hosting/server side the hope was to containerize it which means rolling up all the dependencies etc in to a single slick install that you can add to your system with a few commands and update just as easily.
The host operating system that runs the relevant container will likely be linux to avoid supporting multiple OS platforms as that cross platform back end support has sapped a lot of energy that could otherwise move the GC platform forward.
That being said, the VirtualBox virtualization platform is free for non-commercial use and allows you to run a virtual instance of Linux on a windows or MacOS based PC and then within that you can run the container. If you’re not familiar with virtualization, think of it as an entire virtual PC (BIOS, hard drive, video, network, USB, everything) running as an application inside your main PC.
It sounds complex but it is possible to make snapshots of the virtual machine setup so that is only a few clicks and commands to download and install and the virtual machine image and embedded within it (and update-able from within the virtual machine after that) can be a working WGC instance.
The end result is you would click to launch the VM, adjust a few settings for your host hardware if necessary, and it could auto-start WGC inside of that and you’re off to the races. It’s actually more complex to explain than it is to use but the end result is you would be able to be a windows or MacOS user and host WGC using the virtual machine w/container model.
Alternatively, for heavier users, I believe the desire is to target the RaspberryPi as a dedicated web server/host running the WGC container. This means you don’t need to leave your full spec PC on all the time and can use a $35 Pi over ethernet or wifi and leave it next to the Maslow all the time and access it from any device.
Hosting on a Pi also opens the door for extra monitoring via a camera (the Pi has an affordable HD camera option) and other GPIO controls perhaps, open to the imagination on how to embrace and extend from there. The nice thing about targeting a Pi is it is a fixed hardware environment so it removes a lot of the variability and “my setup is unique because…” complexity of supporting things. The virtual machines help a long way in abstracting it but it’s still a bit more work.