The Register interviews Opera CEO Jon von Tetzchner
14 CommentsPublished August 19th, 2007 9:23 PM EDT By Daniel Goldman
The Register published an interview with Opera’s founder CEO Jon von Tetzchner. The interview covers many areas of interest to Opera users: desktop, Opera Mini, Opera Mobile, Firefox, Opera Widgets, Mobile browsing, security and site compatibility.
Reactions in the blogosphere:
“I believe that the future of browsers is in open source based engines, just because the nature of browser engines suiting perfectly for open source development, but Opera keeps proving me wrong along side the massive IE.”
(Source: Northern Dialogue)
“Great interview”
(Source: Open Gardens)
Update: Here’s a Slashdot discussion on this interview.
If you enjoyed this post, then make sure you subscribe to my RSS Feed.
using
I love how he takes a jab at Google by citing how one person (xErath) fixed so many bugs with his UserJS.
using
lol, I guess it was a bit of grammar that I didn’t realize he was talking about xErath. I though Jon was talking about somebody at Google, which was probably wishful thinking for me at the time.
Anyway, I think this interview shows Opera’s core principles, and also why I love using it so much: The engineering behind the scenes is astounding, nothing already existing is sacrificed (too much) to innovate, and hastily made compromises are kept to a minimum.
And although my major at college is somewhat unrelated from software/web development (environmental engineering), I will certainly keep Opera’s design process in mind through my studies. But there is always that slight possibility I could change my major…
using
My congrats to xEarth! You were mentioned on Register!
using
“I love how he takes a jab at Google by citing how one person (xErath) fixed so many bugs with his UserJS.”
if you look into the code xErath wrote you’ll see that, fuxed bugs are divided into opera bugs and google bugs. and i have to say, that there are lots of opera bugs. so even if google code would have been 100% correct it still would fail. google services failing in opera completly isnt as one sided game as opera would like it to be.
using
Good interview. Thanks.
using
using
@Dante
Perhaps he didn’t want to go about explaining UserJS?
using
whatever: nothing else Google (and any Webdesigners) does for IE, FF and Safari: work around specific bugs in the browser or in other words use the features that are working and leave out the rest. It should be easy for Google to do this as one man could actually do it – congrats xErath
using
problem is, that these fixes (workarounds around opera bugs) makes google pages very slow, and some cant be fixed.
some of these ‘bugs’ are lack of features, not real bugs btw. features, that are present in IE/FF for years.. it always made me wonder why opera decided to spend time on svg that was a shadow to flash, and it was sure that it will never be adopted, instead of fixing their implementation of JS. and please, no standard rhetorics, if you are so standard lover, remove innerHTML implementation.
that question id like Jon to answer, abut in detail, not ‘we are working on it’
using
This whatever guy sounds like whatever2 (same arrogant tone, same typos and same hate for standards). He/she has been flooding the desktop team blog for a while with rants, drivel, off topic comments and useless wannabe tech remarks. Most of it was removed by mods so I guess he has decided to bring all the **** here… hide your kids, people…
using
@Whatever Those are just straw man arguments , what “features”? And what do these “features” have to do with google?
Opera have all the features google need to code for it, although they don’t test in standards compliant browsers first do they? …
using
go to xErath script and look inside, see fixes caused by opera bugs/limitations, and by google itself. i say, that numbers are almost equal.
and features? opera does not support setters/getters (yahoo used to use these, most probably use them up to this day). does not support oncontextmenu (due to inbuilt right click menu), does not support overflow-x, overflow-y css properties making pages look strange with vertical/horizontal scrollbars appearing randomly. list is longer, but i stopped following it as it ceased to be my job some time ago.
afaik these limitations are fixed in 9.5, but question is, are they fixed in a way other browsers use them, or in an opera-way. world is going nothing but ignore too-standard implementation, that doesnt match commonly used one.
and again, if you think browser should be as standard compliant as possible, remove innerHTML. it isnt a paper standard, it is ’standard’ because everyone use it. the secon case is THE standard. id prefer to have all browsers work the same, but due to lots of gray areas in w3c docs, this isnt possible. and stupidiest way of doing something is to implement something in a way different than all other browsers do it. opera did that many times before and now it is paying for it. i hope that they’ve learned their lesson.
using
SVG is huge in the mobile/device space. You would be surprised.
No one argued that innerHTML or such things should be removed, by the way. Straw men will get you nowhere
using
Just great! I could read a J-v-Tetzchner interview every day.