But I digress. I'm here to discuss the good news about the transition to WebKit. Some have worried about performance issues. Others about how Opera will handle heavy loads. And even some about issues with Java in Opera. There are probably a lot of other concerns. The problems with performance and heavy loads in Chrome, which uses WebKit and V8 as engines, are in a lot of the cases caused by their multi-process approach to tabs. Opera Software will be able to roll their own implementation, so they will be able to choose another approach to tabs. As for other performance problems, I'm sure Opera Software won't rest until they get WebKit and their implementation of it up to par with that of Opera today. When it comes to Java problems however, I'm not so sure. It might boil down to how WebKit treats plugins, or it might be a whole different beast alltogether. All I know is that I believe Opera Software will take concerns about things like that seriously. After all, the future of Opera as a desktop browser depends on it. I suggest you all use the Opera Forums diligently and voice your concerns in related and new discussions there.
If Opera Software can solve the technical problems caused by a transition to WebKit, I think there are good things to come, both for Opera users, Opera Software and Opera's partners. After the transition, the browser blocking and layout issues will have mostly vanished. Though the way devs target WebKit is the problem that caused the death of Opera's old engine, Opera users will probably no longer face the problems that plagued the old engine. But there's more. Opera Software will be able to free up resources to work on the user experience, features, and services available to Opera users. The real winners here are Opera users themselves, and if everything goes smoothly, Opera Software.