Originally Posted by Redbullsnation
Ah cool, m8. Maybe next year the boys can port a windows version to make everything simpler. However, now, I don't have to use that crappy mlb.com site to watch
The VMV (virtual machine version) is actually not a bad solution. Considering that web browsers and Flash plugin both seem to consume enormous amounts of memory these days, the 512 for the VMV actually seems reasonable. At least, VirtualBox caps it to 512 whereas Chrome/Flash continue to suck memory until they crash or you have to kill them. VMV boots fast and is quick to setup.
The one drawback to VMV is the lack of persistence (e.g. having to edit the configuration each time you boot the VMV.) I have some ideas on that such as:
* a login screen when config is absent.
* an in-app way of setting favorite=
* a portable (Windows and *nix) way of picking up system time and timezone data from the host OS (though the tzdata screen is really not a bad hack right now)
* a way to update to the latest SVN when VMV is started
Or I can just look into what it would take to enable persistence: perhaps a small <10 mb partition just for ~/.mlb as part of the OVF definition.