Month: January 2010
Judging a “tablet”(?) by its cover
Apple anounced the iPad recently. The response of one corner of the Internet: http://i.imgur.com/oRffH.jpg.
Skimming
through Apple’s iPad page makes it clear that they do not consider it a
stand-alone device like other tablets, but an adjunct to some other
system. What other fully fledged computer has requirements listed for
other computers (http://www.apple.com/ipad/
To be sure, form factor matters, and I suspect that there’re a
bunch of people out there that’d like something like an iPhone only
larger, and now they can get one. Except that apparently the iPad
doesn’t do voice (the 3G section of the specs says “data only”).
*sigh* Way to miss the boat, Apple.
It doesn’t hurt that it can run iPhone apps and there’re thousands
of iPhone app developers waiting in the wings. It has a pre-built
developer community and approximately zero learning curve if you’re
already an experienced iPhone developer.
My basic reaction: Meh. Sorry, Apple. 🙂 I guess I’ll stick to my Mac Pro and my iPhone.
Update 5/11/11: I got an iPad2 last month. 🙂
VirtualBox doesn’t suck
I wanted to run Linux on my Mac laptop, but didn’t want to pay $80 for VMWare Fusion if I could avoid it. It turns out, I could! I’m not actually done installing Linux yet, but VirtualBox seems pretty nice so far.
I wouldn’t bother, since Mac OSX is a Unix variant, but I recently got the hankering to run my Lispworks for Linux on my laptop, so that’s what this is about.
Update: Finished installing Linux with KDE. Worked out of the box. Currently running konsole exported to the regular Mac X11 server.
Update 2: Hit a bit of a speed-bump on VirtualBox: networking. The default NAT networking is great: it will take packets from the guest and put them on the host’s network. But … what if you’re currently unplugged? Then your machine has no network, and no IP address. Sure, your guest can’t get to the outside world, but here’s the thing: It can’t get to your host, either.
So, try bridged networking. As near as I can tell, the network you’re bridging to has to be up and active.
Then there’s host-only networking. The guest can talk to the host even if the host is not currently attached to a larger network … but even if it is, the guest can’t talk to said larger network.
You can switch between the two, but only if you reboot the VM.
I shall attempt to enquire at the VirtualBox forum.
Update 3: While typing in my question at the VirtualBox forum, I thought of a possible solution, which I tried and it works: Add a 2nd NIC to the guest. One NIC is NAT’ed to the outside world, the other uses “host-only” networking to talk to the host. Still curious if there’s a better way, though. My VB forum question here.