« September 2011 | Main | February 2012 »

November 28, 2011

The mixed legacy of Steve Jobs

Over the years, it’s been fascinating to watch Apple mainly due to Steve Jobs, its charismatic CEO who died as of writing this column.

Jobs was fantastic and flawed at the same time. He refused to take part in the industry-wide race to the bottom and instead relentlessly focused on excellence and insisted on being different. I for one appreciate Jobs dragging an entire industry out of the boring beige box mind set and in fact, changed the world a number of times.

Thanks to Jobs, Apple didn’t have to be first with technology, but yet managed to own entire markets. Take the LaserWriter printer for instance: Hewlett-Packard launched its LaserJet a year before Apple got its variant of the door.

Both printers used the same Canon engine, but the LaserWriter could be used with Macintosh computers that had a graphical user interface so you almost saw what you got.

What’s more, the LaserWriter had Postscript that made curves smooth and output sharp and legible. As a result, Apple ended up being the first port of call for desktop publishers, a market that didn’t exist before the eighties.

Thirty years later, creative people still worship Apple products but now, the ranks of Mac Marines have swelled considerably. Business executives strut around with iPhones, iPads and Macbook Airs; Microsofties love Mac hardware and dual-boot into Windows, something you didn’t see before.

It’s a remarkable story of perfection, one that Jobs pulled out of the ashes of many abject failures, but there’s a darker side to it as well.

Maybe due to his chaotic life in general, Jobs loved being in total control. That control extended to eliminating what many saw as potential revenue raisers, such as Apple-clones. On returning to Apple, he killed off the operating system licensing deals with clone makers. Later on, lawsuits against cloner Psystar were launched.

The culture of control and secrecy at Apple manifests itself beyond the products. There’s a general refusal to deal with media, and Apple goes beyond that, using legal action to silence outlets and blogs. Despite those ”1984„ ads and Macs being the darlings of creative people, Apple and freedom of expression didn’t sit well with each other under Jobs’ direction.

Nowhere is that more clear than in the way in which Apple controls features, functions, imagery and text of everything that goes into the hugely successful iTunes and App Store.

With this desire to control every step of the way, it’s curious that Jobs and Apple didn’t take full charge of how its devices are made, an area where it could be the leader and earn a huge amount of kudos simply by ensuring decent labour standards.

Owning an Apple device is a great experience, but you don’t want to be the poor sod in an Apple OEM sweatshop making one. Child labour, workers falling sick from poisonous chemicals and low wages are a shame to the IT industry as a whole, but it jars harshly with Apple’s otherwise slick image and should be new CEO Tim Cook’s first priority to sort out.

However, Cook has some pretty big shoes to fill and his first steps have been wobbly.

Take the launch of the iPhone 4S. It’s not a bad piece of kit. Dual-core processor, hardware accelerated graphics, much improved camera, and new services like Siri voice recognition and iCloud storage.

It also has the same, excellent Retina screen and impeccable design as the earlier version and should sell as well as its predecessors have.

The reaction to the iPhone 4S said was surprising though: while Cook unveiled the iPhone 4S, Apple’s share price dropped.

People were disappointed. It wasn’t an iPhone 5, and the improvements were evolutionary, not revolutionary this time. I felt disappointed too but I wasn’t quite sure why.

Then I realised what was wrong: the iPhone 4S was pretty much what everyone expected. This time around, we didn’t get the surprise new design, feature, product or service from Apple, ”just„ an improved iPhone.

It’s ”better sameness, not revolutionary change„, which is the innovation stifling stuff ex-Apple employee Guy Kawasaki says comes out of customer market research, and the very thing Steve Jobs tried to go beyond.

Apple isn’t about safe plays and gradual improvement, but drastic, eccentric strokes of genius combined with ruthless business ability. That’s a very difficult equation, but Jobs solved it. All eyes will be on Cook to see if he too can do it.

Juha Saarinen

November 3, 2011

The painful road to IPV6

Recently, I’ve had the opportunity to not only do some research around our new Internet addressing protocol but also become fully IPv6 enabled. Not me personally - I’ve yet to get that Ethernet implant sorted out - but my internet connection and the devices that hang off it are now IPv6.

Yes, it’s 2011, and I’m finally using IPv6 natively and not via a tunnel over IPv4. The new protocol comes courtesy of my ISP, Snap, alongside a rare beast: a Fritz!Box VDSL2 router that understands IPv6.

You might think that IPv6 is very slow in coming and you’d be right. Shifting to the new protocol has become an enormous task, one that grows every year as the older IPv4-based internet expands at a huge rate.

Right now, the IPv4 network is larger than the four billion or so addresses it contains. That’s because of Network Address Translation or NAT. This was a hack devised in the 1990s to deal with address exhaustion - yes, that uncomfortable problem has been known for a very long time.

NAT ”hides„ a huge number of networks behind one or more internet-routable addresses. If you have multiple gadgets running on a LAN managed by a single router in your home using DHCP, that includes your network. This saves precious IPv4 addresses, but it also breaks the end-to-end principle of the internet and leads to undesirable effects such as port exhaustion: each TCP and UDP address is limited to a maximum of 65,536 ”ports„ over which the actual bytes flow, so if you have a single, routable IP address that serves thousands of NAT’ed ones, performance on sites like Google Maps that open hundreds of connections will suck.

NAT also adds complexity, can be difficult to scale, and it has arguably slowed down the uptake of IPv6.

Due to the big address space in IPv6, there’s no need for NAT. Until all the billions and billions of devices behind a NAT gateway become IPv6-enabled - and some won’t ever, as they’re too old - that address saver isn’t going away however, and nor is IPv4.

This is one of the big challenges with rolling out IPv6: not only do you build a new internet and give existing devices a new address; you also have to make it coexist with the old IPv4 internet which is still growing, thanks to NAT.

In practice, the dual IPv4-IPv6 stack internet leads to some annoying problems. Software and operating systems are normally designed to use one address type or the other. If a connection over IPv6 is slow to establish or fails completely, falling back to IPv4 can take many seconds. There’s no indication to users what’s going on, either. So, for example, in your web browser, you may just experience blank pages and sometimes, time-outs.

A new algorithm called Happy Eyeballs is at the IETF Internet Draft stage, and it attempts to fix the dual-stack failover problem by switching over faster to, say, IPv4 as well as remembering which connections don’t work.

Another issue that I noticed is that IPv6 network paths aren’t as optimised as IPv4 ones. Google over IPv4 is served to me via a local cache, a mere 6ms away. Over IPv6, it the latency is anywhere from 60 to 330ms. Not a show-stopper and it will be sorted out eventually, but there are many similar cases featuring large content delivery networks and caches.

In simple terms, people aren’t going to want IPv6 if time-outs occur when they browse popular sites like Facebook, or if the performance is really slow due to high latency and constricted pipes.

Even if your ISP does provide IPv6 connectivity, getting it up and running isn’t easy. The vast majority of new operating systems know about native, tunnelled and 6to4 IPv6. Your smartphones and tablets most likely do too. However, the DSL modem that connects you to the internet probably doesn’t, or only badly. Finding residential and small business network gear that supports IPv6 can be difficult, unfortunately.

On the security side, it’s worth noting that dual-stacks can lead to end-to-end connectivity being established over IPv6 to vulnerable devices. IPv4 firewalls are a dime a dozen on consumer gear but IPv6 ones are an unknown quantity.

The Fritz!Box I have comes with an IPv6 firewall, but it’s difficult to configure. What’s more, while the admin GUI on the Fritz!Box provides ample info about what’s going on with the NAT’ed IPv4 network, it only shows the IPv6 address on the router’s internet-facing interface. More work needed there, I’d say.

Even with all the problems mentioned above, IPv6 is worthwhile and yes, you should nag your ISP about having it turned on. The only way we’ll get more choice of residential routers, improved network paths and performance and more is through more IPv6-enabled customers. It will be something of a slog though, so be patient.

- Juha Saarinen

Subscribe
Newsletter & SubscriptionsPC World is New Zealand’s top selling computing and technology magazine.

It provides up-to-the-minute editorial, insight and buying advice for personal computing, cell phones, game consoles, digital entertainment and broadband.
SIGN UP
PCWorldUpdate
PC World's weekly round-up of tech news, gear and game reviews, software selections, and handy How Tos.