Category Personal

My new Macbook Air arrived!

OK. I’m going to gush a bit. Whatever its faults, and however often Apple displays a contempt for customers (and believe me, anytime I want something outside the narrow box they sell, I’ve experienced it), sometimes they connect with the pitch and hit it straight out of the park.

It’s a simple thing these days to do just-in-time manufacturing and shipping from China, and I wasn’t expecting my Macbook Air until Feb. 12. But Apple pulled the shipping date in by a week, and was going to deliver it on Feb. 6th. I was thrilled.

It arrived this morning. Sure, it’s not that complex, but boy, do they know how to make a tech geek happy. The packaging is gorgeous — a coworker said it reminded him of a Tiffany’s box. Even the Apple skeptics in the office — the dyed-in-the-wool, live-in-Redmond-even-though-they-don’t-work-at-Microsoft types, were drooling just a little bit. When they thought I wasn’t looking. They know who they are, and today I can see that their snide comments about Apple and the Cult of Steve are just envy wrapped in sarcasm.

Then you unpack it, and the Air feels both lighter and more substantial than you expect. The screen is terrific, the keyboard very nice, and the overall experience is exactly what I hoped a subnotebook from Apple would be. Even the “Remote CD/DVD” thing works perfectly for installing software — although I bought an external Superdrive, mostly because the remote thing doesn’t work well for playing DVD’s due to the copy protection schemes.

I’m sure after a couple of days or a week of using the machine daily I’ll have the usual list of gripes, wishes, etc. But not today. Today I’m sitting on the sofa, having loaded LaTeX, Office 2008, and a few other essentials, and just enjoying that “first day” experience.

Wow. Bravo Apple.

Screen sharing in OS X Leopard

I have to say, lately I’ve been using screen sharing in Leopard a great deal, to work more flexibly around the house. This isn’t much of a concern in Seattle, since my apartment is small enough that I rarely have to move my laptop at all, but at home on the island, I often find myself wanting to work from the living room or by the windows, but not wanting to interrupt some long process I’ve got running over wired ethernet. So I leave my machine where it is, and use a different machine to work from downstairs via screen sharing. No more copying files around, worrying about having every application on every computer, synchronization issues, etc.

Of course, I used to use VNC for this in a limited fashion prior to Leopard, but the way Apple has integrated this into the Finder networking list and with account security is very nice.

And, when my Macbook Air arrives in February, I can really move around, but without worrying whether I can do “heavy” work given the smaller hard drive and memory footprint, since the Air can be just a light “terminal” for a larger machine.

I know, not problems that most people have, but it’s a nice feature of Leopard that I’m coming to really appreciate.

Sunday Night Windstorm, and What I’m Doing and Studying

I just came in from standing on the deck, under clear skies, a partial moon, and the most amazing windstorm. The moon made visible the big waves crashing on the rocks below me, and the whitecaps out in the channel. It’s been blowing hard all day, without cease, and I’m happy to be inside with a wood stove and food on the stove. A brief respite at home before another stretch at the office. I haven’t quite figured out the optimal amount of time to spend down in Seattle, but I’m pretty sure it’s shorter than I’ve been spending as things heat up at work. Seeing friends and doing things in Seattle is great, but I miss the island. The slow process of meeting people and “becoming a local” has all but stopped as I commute back and forth.

I haven’t written much here since late December, but only because life has reached a fever pitch again, and the brief times I have free away from a full schedule need to be devoted to research and my dissertation, not idle contemplation for my website. But we’re in the thick swamp of an election season, unseasonably early of course, and I haven’t written anything about the candidates, the primaries, the debates, as I did for much of 2004. I can’t promise to get back to regular posting before Super Tuesday, but I hope to soon thereafter. Or as soon as I can get my two projects more firmly underway (one paper, one poster) for the SAA (Society for American Archaeology) meetings in late March in Vancouver. Both are co-authored with Alex Bentley and Carl Lipo, and we’re working on the statistical consequences of expressing formal models of cultural transmission within realistic social networks.

For those unfamiliar with cultural transmission, this is the observation that humans are not born with a hard-coded set of cultural behaviors (in the sense of genetically transmitted) but learn, over the course of child development and throughout life, ways of behaving and believing and thinking through interaction with others in our social groups. In a formal sense, cultural transmission is modeled mathematically through analogues of haploid population genetics models (Wright-Fisher and Moran processes), replicator dynamics and allied models from evolutionary game theory, and the contact and voter models in the study of “interacting particle systems” or spatial stochastic processes by probability theorists and statistical physicists. An open question, whose likely answer is “yes,” is that these methods of modeling cultural learning and transmission are formally equivalent, given appropriate variations of population structure and the focus on deterministic versus stochastic models. But more of that in future posts, hopefully.

Basically, I’m working with some collaborators studying models of social learning and communication, for predictive ensemble or spatial statistical “signatures” in cultural data which are mapped spatially and dated temporally. A “signature” would be a unique pattern of statistical properties which tells us how a given population was structured (in terms of social networks) given the results of how cultural information flowed within the population, and came to be reflected in material objects or artifacts. An example would be a model in which we learn about, and adopt, preferences for songs and music from our social network of friends, but in an unbiased fashion — we occasionally adopt the preferences of a colleague or associate. What statistical properties does this local process of imitation have, when projected into a “global” perspective — statistical patterns within a population, spatial patterns in kinds of data we can map and chart?

Of course, we all know that the model I just described is pretty simplistic. Nobody “just copies” their friends, let alone doing so without any filters, biases, and on a strict “coin flip” or probabilistic basis. But it turns out it sure can look that way when you aggregate the results of many people imitating, choosing, learning, and adopting ideas. So this kind of model is a good “null hypothesis” for a simplistic kind of cultural communication — anything more realistic will have to depart from this simple random model in striking, hopefully unique ways.

Being able to find unique, predictive patterns from more complex models of cultural learning and communication is possible, but not guaranteed — it is easily possible (maybe even likely) that several different kinds of social situations could lead to the same overall patterns at a local, regional, or even global level. We call this problem “equifinality” — the data we have are insufficient to distinguish between several possible processes, so given our models and data, each process is “equally likely” to have caused the observed pattern.

This type of research is what I’ve been engaged in for a long time — at least since 1995, with conference papers, publications, and Carl Lipo’s dissertation research covering some of the results. Now I’m extending our previous work and learning a lot of math, probability, and population genetics in the process. It’s fascinating stuff, but in addition to the job at GridNetworks the work keeps me pretty busy.

This is all by way of explanation for my longish absences from writing something here. I hope to remedy that, as I said, but there’s some serious work between now and then.

Sorry for the interruption…

I haven’t given much thought to writing lately; or more accurately, I often think about writing but typically on flights back and forth from home to Seattle, and I never get the chance once I land and get swept up in the hustle and bustle of things.

The new job is kicking my butt, in terms of schedule. We have a lot to do in a short time, given how hot the HD and P2P video markets are these days, and I’ve been thrown into the deep end of the pool. But it’s good, and in a few months I’ll have a handle on the many projects I’m driving, and I should be able to return to research and writing more frequently.

Carl Lipo and I also need to get the next issue of JEHS prepared and published, and I apologize for the delay on that score, for any of our authors who are reading.

More Leopard Woes: Kernel Panics in Time Machine

This weekend I started experiencing kernel panics in Leopard. I’d gotten a brand-new 500GB external drive for Time Machine, and turned it loose backing up my Macbook Pro. This worked fine for a day or so, until last night when I started getting kernel panics every time I connected the external drive to the laptop. I can attach it before boot, and it panics during the boot cycle. Boot without the drive, attach it after the machine is up and running, and it panics within a few seconds.

The grey window-shade of doom is starting to really bug me, I gotta say.

It’s a known issue, at least to some Leopard users. Apple has not answered the thread yet, or produced a fix or even diagnosis. It’s early days, but I return to my opinion from a previous post: this operating system wasn’t done baking yet, and Apple took it out of the oven too early. Like a cheesecake that hasn’t set, it’s wobbly and collapsing.

Naturally, everyone says the fix is to turn Disk Utility loose on the external drive, but my attempts to do so thus far have failed because the system panics before I can do so, even if I start Disk Utility running and then attach the drive. Tonight I’m going to boot from the install DVD and run Disk Utility, and see if I can get further. Nevertheless, it seems like unless it’s a simple problem, the solutions here are: (1) Don’t trust Time Machine yet, and (2) Reformat my Time Machine drive and start over.

I seriously hope Apple is burning the midnight oil bugfixing and getting a 10.5.1 ready, because if they think Mac users will be happy to regress back to customers-as-beta-testers mode like most Windows releases, they’re in for a shock. There’s some nice stuff in Leopard, but not nearly enough to live with kernel panics, spinning beach balls, and other weirdness.

Java on Leopard: Is it “Horribly Broken?”

Early reports concerning Java 5 on Leopard aren’t encouraging. John Gruber and Adrian Sutton hit back with blog entries, variously arguing either that the breakage isn’t important given shipping compromises, or that it isn’t really broken and that whiners should shut up.

My personal experience is that it’s broken in some significant ways. I’m not that concerned, given the scientific and mathematical programming I do, with Cocoa pipelines and graphics, but overall my fairly simple numerical simulations using RepastJ 3.1 run several orders of magnitude slower in Leopard than Tiger, given Log4J text logging in debug mode.

You can argue, as Sutton probably would, that nothing fundamental is wrong and that I shouldn’t judge “brokenness” by the performance of text I/O, but hey, let’s face it, if you can’t write ASCII text to a bloody text file before protons decay and the sun burns out, then Java 5 is horribly broken in Leopard.

Which sucks, because although Gruber doesn’t see any “significant” software being written in Java for the Mac, there sure are a lot of us using IntelliJ IDEA doing Java development on Intel Macs, and the compile and test cycle just got a lot worse. A *lot* worse.

Leopard was late, and compromises needed to be made, and sure Apple took a lot of flak for announcing the delay, but this OS needed more time in the oven.

UPDATE: This turns out to be the Quartz rendering pipeline switch, and is “fixed” by passing the following to the JVM as command line arguments:

-Dapple.awt.graphics.UseQuartz=true

My guess is that Apple might release a separate download to restore the Quartz pipeline as the default, but in the meantime this seems work. I would like to thank Pratik from Apple, who saw my post a couple of minutes ago and pointed me in the right direction.

Maybe Gruber and Sutton are right, it’s possible we all need to chill out a bit. This here upgrade might turn out to be alright, though I did follow Siracusa’s lead and turn off the pseudo-3D dock using the “no-glass” attribute — I have a zillion program icons and they’re incredibly hard to distinguish at very small sizes in pseudo-3D. Siracusa is also right, it’s almost impossible to read the very-similar grey “stacks” folder icons when my dock is so small….