4 ms·
> try it out on a BeagleBone Black and tinker around a bit with it I've seen statements to this effect around, and it's kept me puzzled. Why ditch a VM that ru
by winter_blue 12y ago
> try it out on a BeagleBone Black and tinker around a bit with it
I've seen statements to this effect around, and it's kept me puzzled. Why ditch a VM that runs on your main dev computer, and instead opt for a BeageBone, rPI, etc.? With a separate computer (like a BeagleBone), you have to copy over the OS ri it each time after building it, and this takes up a small amount of additional effort and time (that could add up). Aren't VMs are faster for someone who wants to do a lot of tinkering and iterative OS development?
- metafex 12y agoIt's basically for the fun of it. Trying out exotic hardware and getting out of your comfort-zone. For me it's just exploring things and maybe a reason to dust off those gadgets and play around with them. OTOH VMs are of course faster, more practical and even sometomes more reliable. For anything serious I'd be using one (and even am, for work, etc.)
- fSnElPKhpdN6xzY 12y agoVMs behave very different from real hardware. VMs are convenient have some very nice features, e.g. GDB debugging with QEMU. But if you're doing anything with hardware, you'll have to test on real hardware or everything will break the moment you do.