My OperaMe, I and myself
Saturday, October 27, 2007 1:16:09 PM
I'm a core developer at Opera. To most of you this doesn't say much so let me start by presenting the core department. In the Opera browser there are much code that is the same regardless if it's used on the Nintendo Wii or in the desktop browser or in a phone, or in a set top box. This part is what we call the Core. There you find the HTML layout engine, the XML parser, the EcmaScript compiler, the DOM environment, the SSL encryption, the SVG layout engine and many other small and big things. In general most of the things you expect from a browser except the user interface. Platform teams then make this into a finished browser (or browser SDK). One example of such a team is the desktop team.
The core department, while being only a small part of Opera, is one of the larger departments and we're actually located at two different geographic locations, Oslo in Norway, and in Linköping in Sweden. I'm in Linköping along with roughly half the core, and I'm mainly working with scripting and document loading and parsing in a small group working with, hmm, scripting and document loading and parsing.
I've long been thinking of starting a blog about work, where I can vent our successes, frustrations and share generic technical information that never really makes it to the changelogs. I don't know how often I will write, and I will have to read our blog policy so that I don't do anything wrong. The blog policy is very free but Opera is after all a public company so there are certain rules. Like, even if I know that we're delivering the browser to the space shuttle and I'm very proud of all the work done to make Opera space compatible, I couldn't say so until the official press release or I would make the stock rate rocket in a way not allowed.
The core department, while being only a small part of Opera, is one of the larger departments and we're actually located at two different geographic locations, Oslo in Norway, and in Linköping in Sweden. I'm in Linköping along with roughly half the core, and I'm mainly working with scripting and document loading and parsing in a small group working with, hmm, scripting and document loading and parsing.
I've long been thinking of starting a blog about work, where I can vent our successes, frustrations and share generic technical information that never really makes it to the changelogs. I don't know how often I will write, and I will have to read our blog policy so that I don't do anything wrong. The blog policy is very free but Opera is after all a public company so there are certain rules. Like, even if I know that we're delivering the browser to the space shuttle and I'm very proud of all the work done to make Opera space compatible, I couldn't say so until the official press release or I would make the stock rate rocket in a way not allowed.
