This is the city: Los Angeles, Calif. Every year, millions of tourists flock to this Mecca of stardom and glamour, hoping that some of it will rub off on them. Sometimes they’re geeks. My name is Turner. I carry a MacBook.
This is your somewhat delayed Developer Week in Review, coming this week from the Mondrian Hotel in Hollywood, a place where the laws of reality have become so distorted that paying $6 for a can of soda has actually begun to seem reasonable. There was no WIR last week, as I was trapped in an alternate universe full of hotels with Wi-Fi connections slower than dial-up. 20kb/sec, swear to God!
We’re wrapping up our West Coast trip this week, a vacation that has been warped somewhat by the presence of my 16-year-old son. Certainly, if my wife and I had been traveling alone, we would not have taken a ride on a Nike Missile elevator in the Marin Headlands, or toured a WW2 submarine. Not that I’m complaining, our side-trip to the LA Gun Club this week to shoot semi-auto AK-47s and AR-15s was definitely a blast (pun intended).
All your patents are belong to us!
Continuing the massive arms buildup of patent portfolios being waged among all the smartphone makers (with the exception of RIM, which seems content to take the role of Switzerland in this war), Google has assimilated Motorola. In addition to super-sizing Google’s intellectual property assets in the mobile space, it also places Google in the role of a direct competitor to the other Android licensees. Until now, Google produced what were essentially engineering development platforms, but no real consumer products. Now that Google owns the DROID (the Motorola version), they’re suddenly in the position of having a strong pre-existing consumer channel.
On one hand, the acquisition makes a lot of sense. Motorola is a pioneer in the mobile space, and the purchase gives Google a lot of ammo to fend off the increasing spate of patent lawsuits being lobbed its way. On the other hand, Google is now trying to sell the Android operating system to companies that it will be selling against. While it’s great to talk about how Android will remain open, the reality is that once Google is fighting for market share with companies like HTC, you have to believe the relationship will become strained at best.
Will a Kzinti invasion be next?
In another case of fiction predicting reality, the last few weeks have been host to a series of social-media-organized protests, which at least in England quickly transformed into riots. Philadelphia and Cleveland fell victim to less widespread but still serious incidents of violence, and San Francisco shut down cell phone service in one BART station after word of a planned protest emerged.
None of this should be surprising to aficionados of classic science fiction, who will recognize the flash mobs now appearing as an eerie echo of the flash crowds described by author Larry Niven in his “Known Space” series. Niven used cheap teleportation as the mechanism that brought large groups of people together at the site of interesting events, but social media is proving to have an equally powerful, if more localized, affect.
Niven also predicted that the presence of a crowd would attract people whose only reason to be there is to take advantage of the chaos to loot and cause mayhem. The big question now is, how much restriction will we accept in this new medium to prevent future occurrences? We are already seeing draconian censorship and invasion of privacy as a result of the battles against child pornography and music piracy, will this be the next battlefront?
Pimp my language
While it seems there’s a new emerging language every week, lots of developers are still being productive members of society with the old programming warhorses. But that doesn’t mean a language can’t get an “Extreme Makeover: ISO Editor”! Case in point, C++ moved into the new decade with the acceptance of the C++ 11 specification.
The new standard brings O-O concepts such as lambda functions and improved type coercion into the language, and it should make the lives of developers still maintaining existing C++ code much more bearable in the future. One must wonder which old-school language will be the next to get a fresh coat of paint. As the old joke goes, if they ever add O-O to COBOL, they’ll have to call it add one to COBOL.
Please send tips and leads here.