xhyve VS Medo

This is due to the way Windows and OSX implement docker. They both use a VM running Linux; Windows uses Hyper-V and OSX uses Bhyve. (https://github.com/machyve/xhyve)

Nowadays, docker uses runc, that is OCI compliant. Docker on macOS uses Hypervisor.framework through xhyve, and is completely macOS native. No VM is used (even under the hood) when running docker on macOS, it's native.

I was happiest with xhyve https://github.com/machyve/xhyve

Serial console in terminal was nice (for me!), network configuration was trash (I think I was able to set the subnet by fiddling around with system plists? and it would revert from time to time), and I didn't have to deal with Virtualbox. I've been away from macs for a while, I don't know if xhyve works on the M1, but it might. I ran a FreeBSD vm so I could run my server code on my laptop in an environment that was like production but slower.

The xhyve fork/port of bhyve for MacOS is worth mentioning: https://github.com/machyve/xhyve

Docker for Mac actually spins up TinyCoreLinux VMs using xhyve that your docker containers run on top of. This is because containers borrow the host kernel, so you can't natively run Linux containers on Mac. Xhyve spawns VMs so a Linux kernel will be present.

There's also been a port of FreeBSD's bhyve to macOS for years: https://github.com/machyve/xhyve (which, in turn, is [or at one point was] used by Docker to virtualize Linux)

I've used xyhve on my Mac to have a FreeBSD VM running a copy of https://www.freshports.org/, including a copy of the database, which runs about 200GB. For dev work, it was fine. I used it when I didn't have [great] internet connectivity, for example, when on the train/plane. When upgrading packages or just doing dev work, it was great.

To me the most impressive recent example is a video editor developed for Haiku OS [0]. It fits on a 1.44MB floppy disk.

[0] https://github.com/smallstepforman/Medo

> does anybody know of an editor capable of cutting between inter frames?

https://github.com/smallstepforman/Medo

I’ve created a 4k UHD video editor for Haiku OS (https://github.com/smallstepforman/Medo), it’s a C++17 native app, with over 30 OpenGL GLSL effect plugins and addons, multi threaded Actor model, over 10 user languages, and the entire package file fits on a 1.44Mb floppy disk with space to spare. If I was really concerned about space, I could probably replace all .png resources with WebP and save another 200kb.

How is it so small? No external dependancies (uses stock Haiku packages), uses the standard C++ system API, and written by a developer that learned their trade on restrained systems from the 80’s. Look at the old Amiga stuff from that era.

At its core, Linux offers variety, while Haiku strives to be a unified system. There is only one official UI, one sound API, one filesystem, one preference system, etc. making Haiku easier to administer. The system kits are designed to work together.

For instance, I created a from scratch video editor for Haiku which does 4K UHD videos with OpenGL based plugins, with over 30 effects, and 10 languages. The installer package with no dependancies is 1.3Mb (fits on a floppy disk). https://github.com/smallstepforman/Medo Under Linux, I would require many more dependancies since I have so no guarantee what libraries or API the users have installed.

My favourite - BeOS/Haiku Interface Kit (Link to my project with screenshot https://github.com/smallstepforman/Medo).

You can always use both ... example from my project: https://github.com/smallstepforman/Medo

Wait until you try Haiku on the same hardware. I’ve got a 4K video editor with no HW acceleration yet is smoother to edit videos than both OSX and Win10.

https://github.com/smallstepforman/Medo/raw/main/Docs/Medo.j...

https://github.com/smallstepforman/Medo It is for a opensource Media Operating System called Haiku Os, and it is less than 1.44 Mb open source very lightweight: