Feeds

Symbian’s Secret History: Davies on what went right (and wrong)

Former CTO Charles Davies shares his memories

Eight steps to building an HP BladeSystem

On creating Epoc

"It was quite engineering achievement. We had to deal with memory leakage, and had to be able to run for a very long time.

"Garbage collectors would have been unthinkably expensive to do at that time, and the processors were too slow to support garbage collection, they weren't up to it.

"We probably went too early with C++. My opinion now is C++ is a pig of a language, it gives you too many ways of doing some things that are dangerous. Java is a nicer object-oriented language. The standard was just solidifying, and we went with our own proprietary exception.

Charles Davies and Colly Myers in 1984

Charles Davies and Colly Myers in 1984. Myers designed the

Epoc32 (later Symbian OS) kernel and was Symbian CEO
from its foundation in 1998 to 2002.

"We actually measured the stacks. The idea is that a stack, which you need for every process thread, is just too expensive. So we were incredibly tight with memory. We'd see how far the stack came down and calibrate the stack on the basis of that. It's an unimaginable world for people used to modern things.

"Android suffers from non-deterministic responsiveness because it has to do garbage collection every now and then. It'll get better over time, but it's an issue.

"I think of Moore's Law as an order of magnitude every five years – and it's just huge. And it changes the nature of the software.

"Symbian was quite demanding at the time in requiring an MMU. The way that the screen was drawn was the only affordable one – which was reactive repaint. The way the window server works is it sends an event all the way to the application when something needs to be redrawn. You don't buffer, in any sense. That evolved over time. It turns into the wrong paradigm when you've got GPUs. For composition with transparent windows, that becomes important. When Windows was XP, a GPU was optional, but when it went to Vista, a GPU became mandatory. It was a similar transition in phone OSes."

On joining Symbian in March 2003

"The key thing was API compatibility – and we succeeded on that. We got far more disciplined in our processes, and as much as not, that was for [the benefit of] Series 60 and UIQ. That was a big thing. [I also looked at] the boundary of where we sat in the scheme of things.

"When I joined Symbian, the organisation wasn’t sure if Java was an application or a system language. I took the view C++ was our system language and Java was more like an application. Java was more high profile in 2003...

"The Japanese were really good for Symbian. They were very demanding on quality and the most diligent in testing, so quality was a huge push at Symbian. People were rewarded on that.

"Then we had Platform Security which was incredibly disruptive – more disruptive than people thought. And we did it in a way that broke compatibility, and said that would be the last time. It was a big kicker. We could have done that better. We could have done Platform Security in a less disruptive way. We underestimated the downstream disruption."

On Apple… and future mobile design

"The time Apple made its first iPhone was about the first time that anyone who wasn't already incumbent could. So timing is everything. Why? Because of the IP, and the signalling stacks – remember the iPhone couldn't manage 3G, but it could just about manage 2G.

"Apple works very hard at things people find appealing. There's a saying that 20 per cent of your functionality has 80 per cent of the appeal, but you never know which 20 per cent it is until after the fact. All companies essentially tinker with product specifications without any certainty of what the market will like, including Nokia and Apple. Apple are working harder at seeing if something is a better fit to the market. There's also something called looking at the user experience (UX) backwards, and Apple is very good at that. But nobody can do it with absolute certainty.

"Perhaps there's a backlash to more utilitarian functionality – like making a phone call. Then there's the value of apps; it's a question of degree, and how absolute that lock-in is. iPhone and Android have a hell of a following, it's tough for Microsoft to catch up; and Nokia almost had it, and threw it away, because of fragmentation." ®

For Part One of this series, on the events leading to the creation of Symbian – see here. For Part Two, the first three years, see here.

Securing Web Applications Made Simple and Scalable

More from The Register

next story
Auntie remains MYSTIFIED by that weekend BBC iPlayer and website outage
Still doing 'forensics' on the caching layer – Beeb digi wonk
Apple orders huge MOUNTAIN of 80 MILLION 'Air' iPhone 6s
Bigger, harder trouser bulges foretold for fanbois
GoTenna: How does this 'magic' work?
An ideal product if you believe the Earth is flat
Telstra to KILL 2G network by end of 2016
GSM now stands for Grave-Seeking-Mobile network
Seeking LTE expert to insert small cells into BT customers' places
Is this the first step to a FON-a-like 4G network?
Yorkshire cops fail to grasp principle behind BT Fon Wi-Fi network
'Prevent people that are passing by to hook up to your network', pleads plod
BlackBerry: Toss the server, mate... BES is in the CLOUD now
BlackBerry Enterprise Services takes aim at SMEs - but there's a catch
prev story

Whitepapers

Designing a Defense for Mobile Applications
Learn about the various considerations for defending mobile applications - from the application architecture itself to the myriad testing technologies.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Top 8 considerations to enable and simplify mobility
In this whitepaper learn how to successfully add mobile capabilities simply and cost effectively.
Seven Steps to Software Security
Seven practical steps you can begin to take today to secure your applications and prevent the damages a successful cyber-attack can cause.
Boost IT visibility and business value
How building a great service catalog relieves pressure points and demonstrates the value of IT service management.