hocus VS projector-docker

I didn't want to go into all the technical details, but we have another write-up that goes into details about RAM management: https://github.com/hocus-dev/hocus/blob/main/rfd/0003-worksp...

Other than making sure we release unused memory to the host, we didn't customize QEMU that much. Although we do have a cool layered storage solution - basically a faster alternative to QCOW2 that's also VMM independent. It's called overlaybd, and was created and implemented in Alibaba. That will probably be another blog post. https://github.com/containerd/overlaybd

If you’d rather use a self-hosted alternative, we are building Hocus [0]. It’s still in alpha, but already supports prebuilds, VSCode, shared environment variables, and more.

[0] https://github.com/hocus-dev/hocus

[https://github.com/hocus-dev/hocus

Check out our product launch post on Reddit here and the 0.2 release on GitHub here.

Although they've basically closed source it since release, Jetbrains Projector was a fantastic tool I've used a lot in the past for that - Just spin up a docker container on my home server and pull out my ipad keyboard

https://github.com/JetBrains/projector-docker

Unfortunately, It's hard to tell if JetBrains Gateway will keep all of the remote dev features or not.

If you have a student package from JB, you can use CLion for Rust development (as do I) and spin up a cloud instance of Clion https://github.com/JetBrains/projector-docker Then you can access it from anywhere over the web.

You can self host Jetbrains IDEs actually! https://github.com/JetBrains/projector-docker

Maybe try using IntelliJ Projector - just run your IntelliJ harmlessly (almost) in the browser :D You can run it simply using docker, run on your machine, or even on the cloud. I have tried to use that for my personal projects and it works.

Worked a lot better using one of their Docker images, but feels like it has too many drawbacks compared to my current VcXsrv setup. Cool stuff though, hope it gets developed further.