News for hackers. Stuff that matters.
Re:Code rot and why I picked OpenBSD by gaius on Sunday January 04, 2015 @04:29AM (#8833939)
The solution I have used for this for well over a decade is Windows on the hardware, then a VM, then my OS of choice running full screen ontop. The overhead of even semi-modern virtualisation is pretty low, and you benefit from power management that has thoroughly matured.
Re:Code rot and why I picked OpenBSD by morganvachon on Sunday January 04, 2015 @10:51AM (#8834720)
I always test drive a new-to-me OS in VirtualBox and VMWare first, just to make sure I can get my head around how it works, but even running it fullscreen on a fast system, it's not quite the same as bare metal. Random slowdowns, unaccelerated window managers, printing not working properly, and issues with some guest OSes sharing folders with the host can be annoying.

Another thing to consider is that bug reports are only valid for the virtual environment; sometimes things that happen there simply don't happen on bare metal. I always test Haiku OS on any new hardware I get so if I come across something wonky, I can submit it to the devs for more testing. In a VM, that's pointless (but then Haiku is a hobby, not a job, so maybe not relevant to this discussion).

All that said, if all you need is a terminal and a web browser to be productive, a VM is a solid choice for getting things done efficiently.

Re:Code rot and why I picked OpenBSD by xtrumanx on Sunday January 04, 2015 @12:42PM (#8835117)
I tried that out and noticed minification and bundling of my js code taking several seconds rather than a couple of milliseconds. Am I doing it wrong or is that to be expected? I was using Ubuntu in virtual box on win8.
Re:Code rot and why I picked OpenBSD by fencepost on Sunday January 04, 2015 @03:03PM (#8835609)
Are available hardware virtualization features enabled in the BIOS?

A little digging brings a 9/2014 comparison of virtualization software that notes VirtualBox as a distant third on performance benchmarks (http://www.tekrevue.com/parallels-10-fusion-7-virtualbox-ben...) and an Ubuntu thread noting that its performance under VirtualBox leaves much to be desired (http://discourse.ubuntu.com/t/virtualbox-or-vmware-for-linux...).

Re:Code rot and why I picked OpenBSD by kcorbitt on Sunday January 04, 2015 @03:10PM (#8835624)
If the files are in a Virtualbox shared folder from the host OS, that performance is to be expected. Just google "Virtualbox shared folder performance."[1] If you're using Vagrant to manage the VM it's easy to work around this by switching the file share mechanism to nfs. If you're not using vagrant, you can do this manually too, or just move the files to a non-shared folder inside the VM.

[1] Scroll down to the graph at http://mitchellh.com/comparing-filesystem-performance-in-vir... to get an idea of how bad this is.

Re:Code rot and why I picked OpenBSD by transpute on Sunday January 04, 2015 @09:56AM (#8834543)
Have you tried Hyper-V as a client hypervisor?
Re:Code rot and why I picked OpenBSD by gaius on Sunday January 04, 2015 @12:36PM (#8835103)
I haven't, most of my experience is VMware (on server farms) and VirtualBox on desktop.