The day has finally come. Opera’s Core team joined the blogosphere with its ‘Opera Core Concerns’ blog.

The Core team at Opera is responsible for the fundamental core of the Opera browser. It’s the rendering engine (and more). It’s what makes it possible for Opera to easily build their browser across all different platforms and devices.

Here’s how the Core team describe themselves:

“What we call “Core” at Opera refers to the platform-independent internal components of our browser. Opera delivers web browsers on more than a dozen different operating systems and platforms, on devices ranging from state of the art desktop computers via game consoles and TVs down to handheld devices with fairly limited processing power. The same Core code base is used across the entire product range. This enables us to deliver the same feature set and level of standards support regardless of the target device.

Being part of Opera for the past couple years, I’ve come to recognize the smart developers and engineers of the Core team. They are folks who truly know and work with the nitty gritty details of Web standards and core browser technology.

What I’d like to see them blog about
Ideally, I’d like to see the Core team blog turn into Hallvord’s blog, but on steroids. Hallvord, who does Core QA at Opera, regularly dissects the issues and problems with sites that don’t play well with Opera.

I’d like to see the Core team blog ‘regularly’ blog about and explain the issues (and solutions) that Opera has with certain sites. The benefits for such kind of blogging are enormous.

1. It creates an open dialog with the Web developers working on those broken sites. Fixing the problems will probably be placed on a higher priority.
2. Not only does it create an open dialog with the developers of those sites in question, it also opens the door wide for the Web developer community and gives them access to our Core engineers.
3. By highlighting the actual reasons of why certain sites break or don’t work in its browser, people won’t view Opera as a sub-par, deficient browser, but rather place the blame on broken code and the developers working on those sites.

In addition, I’d like to see the Core team blog about the enhancements and fixes that are made to the Core code. When new desktop builds are made public, the Desktop team generally brushes over only some of the many items in the ‘Core’ changelogs. I’d like to see the Core blog complement those changelogs.

My hope
I sincerely hope the Core blog will have fresh and interesting content on a regular basis, and that it won’t fizzle after the initial momentum.

If you enjoyed this post, then make sure you subscribe to my RSS Feed.