Feeds

Opera's Jon Von Tetzchner on browser choice, the iphone and Google

The highlights

  • alert
  • submit to reddit

Secure remote control for conventional and virtual desktops

Interview In a wide-ranging interview today Opera chairman Jon von Tetzchner talked about the Browser Choice ruling, Opera's iPhone app, Google as a competitor, and how P2P will be the next generation of the web. Rather than pad it out with waffle, here are the highlights with signposts.

On the EC's Browser Choice screen

The Commission has impressed us. Microsoft is a very big company and the European Commission is a fairly small group of people. A lot of people weren't expecting this decision.

Bundling alternative browsers with Windows was rumoured to be one of the solutions around ten years ago, along with opening up the Windows source code. Then came the 2000 election, a change of administration, and the case was settled about two minutes after that.

It shows the importance of regulation, that the rules are there for a reason. Like a referee in a football match, nobody really challenges their right to be there.

Now people have a choice of a faster, more secure browser. We hope people will try it out, we think we'll come out well if they do. It's also good for Microsoft, too. IE has improved a lot. It now passes the ACID2 standards test for example.

Opera chair Jon Von Tetzchner

Opera chairman Jon Von Tetzchner

[Ed's note: the new randomised browser choice screen doesn't appear if you have FireFox selected as a default browser, only if IE is the default. But it does appear on Windows XP and Vista, not just Windows 7. And it doesn't appear on Mac.]

So we have four browser cores and they should compete on standards, not succeed because one works and another doesn't. These four browser cores are not going away.

On Chrome

You know what Chrome means? It's plating, a skin. That's what Chrome is.

I often say there hasn't been a new browser in ten years. People are surprised by this, but there hasn't been a new browser core for ten years. Chrome and Safari are the same, they're both based on kit, and webkit is based on work by KDE.

Google has done a fair amount of work. It's written its own JavaScript engine, to be fair.

On the per-process model

We actually tried that ten years ago - in Opera for BeOS. The BeOS team were very keen on threading.

We can do that now, but we find f you do things the Google way, you use a lot more memory. It's much more resource-heavy if each page is its own process.

Providing a secure and efficient Helpdesk

More from The Register

next story
Not appy with your Chromebook? Well now it can run Android apps
Google offers beta of tricky OS-inside-OS tech
Greater dev access to iOS 8 will put us AT RISK from HACKERS
Knocking holes in Apple's walled garden could backfire, says securo-chap
NHS grows a NoSQL backbone and rips out its Oracle Spine
Open source? In the government? Ha ha! What, wait ...?
Google extends app refund window to two hours
You now have 120 minutes to finish that game instead of 15
Intel: Hey, enterprises, drop everything and DO HADOOP
Big Data analytics projected to run on more servers than any other app
New 'Cosmos' browser surfs the net by TXT alone
No data plan? No WiFi? No worries ... except sluggish download speed
prev story

Whitepapers

Providing a secure and efficient Helpdesk
A single remote control platform for user support is be key to providing an efficient helpdesk. Retain full control over the way in which screen and keystroke data is transmitted.
Top 5 reasons to deploy VMware with Tegile
Data demand and the rise of virtualization is challenging IT teams to deliver storage performance, scalability and capacity that can keep up, while maximizing efficiency.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
Secure remote control for conventional and virtual desktops
Balancing user privacy and privileged access, in accordance with compliance frameworks and legislation. Evaluating any potential remote control choice.