Does this mean they'll be using V8 too?
Yes it says so here http://my.opera.com/ODIN/blog/300-million-users-and-move-to-...
Opera moves to WebKit
11–20 of 295 posts
Re: Opera moves to WebKit
#12Does this mean they'll be using V8 too?
The press release notes that they're using the Chromium port of WebKit, so it's very likely that they'll be using V8 as a JavaScript engine.
Re: Opera moves to WebKit
#13Does this mean they'll be using V8 too?
I'm curious too! I think Javascript in Opera was a bigger problem than HTML.
A year ago I worked on an app with heavy JS frontend and frontend guys told that they can't make it work properly on Opera.
Re: Opera moves to WebKit
#14Seems a great news but I can't really understand the benefits and differents between Gecko and Webkit, can someone say?
Re: Opera moves to WebKit
#15Now it's time for IE to switch to WebKit as well. Also, they should make it available for all versions of Windows.
Well, it's MSHTML rendering engine is used by many other apps too, for one thing.
Re: Opera moves to WebKit
#16While I agree that webkit is a great piece of software, what happens when everybody switches to webkit? Will Google/Apple/developers simply ignore other engines and let it become the new IE of the decade?
Re: Opera moves to WebKit
#17Seems a great news but I can't really understand the benefits and differents between Gecko and Webkit, can someone say?
For the normal user it does not matter.
It just matters that there are competing engines. As long as there are multiple implementations, we will have a formal standard for HTML and Co. If e.g. everybody (Microsoft,Mozilla) would adopt WebKit, then nobody would bother to extend the HTML standard. Just implement it in WebKit. Soon, HTML will be a mess like Office Open XML.
Re: Opera moves to WebKit
#18"Opera is for people who appreciate choice, and we are going to make it even easier to choose Opera in the future."
That's a nice spin. Less rendering engines, more choice!
Re: Opera moves to WebKit
#19Mixed emotions here. I think it makes every sense for Opera to do this. The cost of maintaining their own rendering engine must have been huge and the advantages it brought were slender.
It's also good to have another major player contributing to webkit.
On the other hand it's a step closer to an unhealthy monoculture in rendering engines. It's already the case for the mobile web that people are starting to define standards as 'whatever webkit does'.
Re: Opera moves to WebKit
#20I worked for Opera the summer of 2010 and I've also been using the browser the last couple of years. Compared to Google, Apple, Microsoft - it is important to understand that Opera is a small, very small, company. I'm very happy to see their resources better used to innovating and improve their exiting product, rather than trying to catching up to the other browsers. A big loss for the general state of rendering plat…
It breaks my heart to know that Presto is going to most likely be left to bitrot in some SCM somewhere.
But on the same note, I understand that using webkit will be better for Opera as a browser.