In praise of hackers and modders

(Edit: I called the i8910 the Omnia Icon in Australia. Actually, that's a winmob device. The i8910 is the HD Icon. Which doesn't sound any less stupid.)

Before I start, let's get a little something out of the way, first:

A hacker is someone who tries to take things apart in order to understand them, and fiddle with them in order to improve them.

A cracker is someone who tries to break things in order to break them for fun and profit.

Right, moving on.

Here's the thing: The world relies upon hackers to advance. Engineers? Hackers, if they're any good. The spirit of "What would happen if..." and "Hey, how does that work..." drives productive creativity and improvements.

Scientists? Hackers, by definition. Hackers of reality and of life.

But the term is a computer one, and it's computer programmers who fiddle who I want to talk about now.

All programmers, if they're any good, are hackers. They want to know how somebody else did that cool thing, they have to chase down bugs in their own code, they're dissatisfied when they see something functioning below-par. They'll sooner spend two days building a replacement than twenty seconds being frustrated.

And they make really cool toys for the rest of us.

Commercial software is built by waged hackers with deadlines and managers. Open source software is built by hackers, some of whom have wages and managers while they're doing so.

And then there's the ones producing not the major product, but the improved version. The one you have to work to get. The operating system that works the way it should have done, if only the company producing it hadn't had commercial obligations or, well, deadlines and managers.

I had a Sharp Zaurus SL5500 for years. It was unabashedly a toy when I got it - a chunky PDA with a QWERTY keyboard and a Linux operating system which satisfied my twin desires of having a cool toy, and being able to type lying in bed. Laptops are too clumsy, too bulky, for lying on your back jotting down thoughts and chasing ideas. Oh, and an ebook reader for Project Gutenberg classics.

Being Linux, an open-sourced system, built using a variety of also open-sourced toolkits and projects, it was only a matter of time before OpenZaurus arose, flexed its muscles, and started producing an alternate, community-built, better-performing, less rubbish software platform.

Okay, buggier as well, but that's the price you pay for development.

I have no idea how many times I reflashed that poor device with new updates, but by the end I could do it in my sleep and it was probably a contributing factor to its eventual, inevitable, demise.

Eventually, however, the SL5500 was replaced with the sexier (black) SL6000, and then the C-series came out with a mini-laptop form factor and a swivelling screen and all the sex appeal that chunky SL5500 never had, and development on the now rapidly aging devices slowed and then stopped, lingering bugs left untreated.

At the same time, my progression through mobile phones landed me at a device with a big colour screen and enough of a java platform to run ebook readers, and then I found a text editor for the phone, and the Zaurus was doomed. The next time I actually tried to turn it on, no amount of hard-resetting, battery-replacing and fiddling would produce the merest flicker of life.

That phone was replaced with a much more powerful one running an open-standards operating system called Symbian with an open-standards interface called S60.

And that brings us neatly to my point, really, because we are now in the realm of smartphones which are more powerful than dedicated PDAs or even laptops of years gone, and one of the defining points of a smartphone is that you can upgrade it.

Which, of course, decent companies do on a regular basis - buy a top-end or even middle-range Nokia and you can confidently expect a new firmware version to bring speed, battery life and functionality improvements every other month for a year or more.

But some don't and, occasionally, others take up the slack.

And then there are those which invite it.

Google's Android operating system is Linux, customised. Which, to geeks and hackers, is like walking into a lion enclosure waving a chunk of dead goat over your head.

While companies pander to network operators and take special note of commercial agreements, hackers cheerfully take the code, rip out the rubbish, port across a cool toy from the next release, drop in something else to fix what everyone except the distributor thinks is a problem, and hey presto! You void your warranty but, frankly, the advantages outweigh that.

If you use an HTC device running Android, you really should be using Cyanogen's replacement ROMs.

Motorola managed to alienate a large community of current or potential users, me included, by preventing this practice on the non-USA Milestone.

It's healthy to have people like this keeping the big boys on their toys.

But let's return to Symbian. The platform, used by nearly everyone but championed by Nokia, who bought S60 and dominated the ecosystem to such an extent that they, in my amateur opinion, damaged its competitiveness, has its roots in 8-bit greyscale devices running for two weeks on a pair of AA batteries, and has been evolving healthily ever since, becoming the most resource-efficient, flexible and potentially powerful of all smartphone systems without, at the same time, really extending itself.

It can support network protocols that are still in the laboratory, but read the international press and you'd get the opinion it's doomed, dead in the water, rubbish, horrible to use, out-dated and slow, part of which relates to S60, which quite frankly is old and has always demanded a little effort to use it properly, and part of which is Nokia being parsimonious with hardware, relying on the efficiencies of Symbian to keep costs down while still providing class-leading functionality.

But then there's Samsung. Unlike Nokia, who cut back on hardware and then spend time and effort optimising the software, Samsung produce truly mighty devices and then just sort of... forget them.

The current king of Symbian, the most powerful and the most impressive, is not the all-singing N97 family but the one-piece Samsung i8910, variously known as Omnia HD (because it was the first phone able to shoot HD video) or, in Australia, the slightly nauseating HD Icon. Great 8MP camera, great stereo speakers taking up each end of the device, great big 3.7" capacitive toughened glass AMOLED screen, 600MHz processor with full graphics acceleration and oodles of RAM.

But the first release had crippling problems, and since then it's had, well, a couple of firmware updates, but not what you'd call love, care and attention from momma and papa in Korea. The C: drive, where the operating system lives, is so small that a couple of system updates fills it. And the discerning smartphone power-user these days demands updates, currency, movement, dammit!

Roll on HyperX. Yes, it's possible to produce custom firmwares for Symbian. Generally, this hasn't been needed, and it's presumably tricky enough that people haven't tried. But for a megaphone like the i8910, hoops were, as the saying goes, jumped through. And even people who normally run a mile from the innocent suggestion that hacking a phone to customise the home screen might not mean the end of the world, have dipped their toe in the water and declared themselves impressed.

I wouldn't be surprised if Samsung sell a few more i8910s thanks to HyperX. I may very well, in the next month or so, be one of them.

Raise your glasses to the hackers and the modders - we wouldn't have got this far without them.

Motorbike accidents in the media: part the .... 9

I really, really didn't think I'd be able to find a 9-cylinder motorbike.

Well, guess what? I couldn't.

There are rumours and hints, the most promising ones centred around another aircraft rotary engine, but I couldn't pin down anything definite. The best lead, complete with photo, turned out to be somebody who didn't check their facts thinking that a monster W3 engine had nine-cylinders. Uh, no.

But, moving on.

The number of stories seems to be increasing. Putting aside my delayed updates, I currently have seven tabs open, some of them dealing with the same incident, and another couple tagged and yet to open. I wonder if this actually represents an increase in accidents, or if suddenly they're more likely to be reported? Hmmm...

From the Courier Mail, from June 4, comes "Speed blamed as motorcyclist dies, passenger critical when bike hits bus at Forest Lake."

There seems to be a definite trend for Courier Mail headlines to get longer without getting any more useful. Personally, I would have started with the death, and left the speed part out of the headline entirely.

A 38-year-old man from Inala was killed when his black Suzuki bike collided with a bus turning from Forest Lake Boulevarde into Grand Avenue about 6pm.

Mentioning the brand, that's rare! He died, female pillion was taken to hospital.

The Forensic Crash Unit is investigating the cause but police said it appears the motorcyclist may have been speeding.

Given the size, visibility and general lumbering nature of a bus, that's likely. However, 6pm in early June is dusk turning into night, and without more details it's hard to tell that the bus driver didn't simply start pulling out and the rider panicked, locking the brakes instead of trying to swerve, hitting the horn, whatever.

There is a little box under the photo which says "The force of the impact can be seen clearly from the damage to the bus", but they must be referring to a different photo. I can't see any damage on the bus, just dirt and age. They may have meant "damage to the bike". The window above the wheel seems to be missing, so maybe the bike hit the rear wheel and the rider went up and through the window.

In which case the most likely scenario is the bike was traveling along Forest Lake Boulevard, which is a major road, and the bus was turning across it. In which case yes, the bike was traveling far in excess of any sane speed. The time it would take for a bus to travel almost all the way across the road is way more than the time it would take a bike to stop from 100, let alone 60.

There looks like there's a lot of information here, but actually: not really.

There is a bonus second entry in this report:

In another serious crash, a motorcyclist suffered multiple fractures after allegedly going through a red light on Kingston Road at Loganlea and running into the front of a car.

The 33-year-old was taken to the PA Hospital with suspected broken legs, pelvis and arms.

The car driver was unhurt.

This is actually a more complete and less frustrating report. It pretty much says everything with no extras and no supposition, and it sadly reads like another case of a dickhead getting caught out.

The article then mentions a single-vehicle car accident and closes with: Queensland’s 2010 road toll now stands at 98 lives lost, 56 fewer than at the same time last year.

Which is surely going to be ammunition for the "speed cameras work" brigade.

For the record: I don't think it's possible to come to that conclusion - there are too many confounding variables and the numbers just aren't big enough. But I Am Not An Ethnographer, and may be wrong.

In summary: not a bad story, but slightly frustrating, not quite enough detail, and frankly the headline is sensationalistic.

From ABC News Online from June 2 comes a six-paragraph story headlined "Man jailed for killing motorcyclist", a sentence guaranteed to bring a glow of sourly retributive "it's about time" satisfaction to any motorcyclist's heart.

Essentially: 70yo man, at Lowood at 1:30am:

The court was told his vehicle was travelling on the wrong side of the road below a crest on a hill when it crashed into a motorbike travelling in the opposite direction, killing the driver.

First of all, Maria Hatzakis, nice economically written and punchy story, but motorcycles have "riders". Only vehicles with more than two wheels have "drivers". The sub-editor really should have picked up on that, as well.

Lowood is a country sort of place, and it's likely there were absolutely no lights other than the vehicles'. Bike came over crest, thought "OH FU..." and crashed, fatally. It is sometimes possible to see lights coming over a hill, not always, and with the spread of lights from vehicles, not with any precision. The driver could also have wandered at the last minute. The driver, remember, was 70.

He has been disqualified from "obtaining or holding" a drivers licence for four years, and I sincerely doubt that he will ever get it back, at that age.

Some of the writing is a bit loose, but actually a nicely comprehensive article.

Also from ABC News Online, from June 5, comes "Motorcyclist charged after police chase".

Now, I've said this before, and I'll say it again: If you're being chased by police, pull over and cop it. There's a slim chance you can challenge whatever they were going to fine you for, but there's no chance if you run away. Evading police is an offence, it's dangerous and you lose any right to plead innocence or mitigating circumstances. You stuffed up: Take the consequences.

And this is why:

In March this year, laws were introduced increasing penalties for people who refused to stop for police.

The change was dubbed Skye's Law after toddler Skye Sassine, who was killed in a crash on New Year's Eve in Sydney's south-west.

Yes, well.

Police say he reached 140 in a 60 zone, they called off the chase after he crossed onto the wrong side of the road, and they arrested him after they found his bike in a driveway.

You see, they have cameras in cars: If they're chasing you, they know your numberplate. They know who owns the bike, and where it should be garaged.

He was remanded in custody.

No sympathy.

This is a tighter-written story, without an author's byline, than the one above with an author's byline. Go figure.

One more, I think, a short one:

From the Courier Mail, "Rescue crew trying to reach motorbike rider who crashed over cliff at Dundas", June 6.

Three paragraphs, of decreasing length. The headline is a little longer than I would allow, but it keeps interest. "Rider crashes over cliff at Dundas" would do equally well. The fact he's still alive and rescue crews are trying to get to him can probably wait for the opening paragraph.

Now: Mount Glorious, 10:40am... I'm sorry, but the only explanation that isn't "he ran out of talent" involves getting frightened by a vehicle, bike or car, speeding the other way. He may have hit gravel or leaves or oil, he may have been doing the speed limit. It's just highly unlikely.

What's astonishing is that the article is so bald it doesn't even mention speed or any suspected cause. Just the barest of facts. Makes a nice change, really.

With that, I shall sign off. Only two weeks behind schedule.