300 million users strong, Opera moves to WebKit comments
Page 2 of 2(63 comments)
Left under the original article, as archived.
JimThursday, February 14, 2013 12:29:10 AM
Webkit has a slow software render and its hardware acceleration is second rate compared to geko.
Not to mention it hardlocks every computer I have tried it on if I browse like I do in Opera!
AGAThursday, February 14, 2013 4:22:44 AM
Opera kill himself whit this
ОлександрThursday, February 14, 2013 11:19:58 AM
I think that is good idea switching to WebKit
Old-NickThursday, February 14, 2013 12:43:03 PM
It's hard to believe you just dropping all these. Presto, Carakan, Vega...
alexvodaThursday, February 14, 2013 1:06:33 PM
As I said on the poll and on other pages:
If the DECISION IS FINAL and IRREVERSIBLE PLEASE OPEN SOURCE PRESTO! AND OPEN SOURCE CARAKAN! AND THE UNITE SOURCE CODE!
If you are switching to Chromium, Webkit and V8 then Presto and Carakan would be considered abandoned, therefore you would no longer have any use for them. So donate what you no longer have a use for to the community. Put them on github along with Dragonfly!
JTGbtThursday, February 14, 2013 3:10:07 PM
Bad news for mobile Opera. All webkit-based browsers for android sucks, now only mobile Opera on HVGA screen have quite usable scaling/scrolling and content reformatting features ._.
PengeThursday, February 14, 2013 5:08:48 PM
Haavard!
What will be the fate of Magic Variables after switch from Carakan to V8? There are any alternatives in the V8 JS engine?
One more question: The structure of profile will change? For example converting INI-s to JSON, etc. which may cause problems in the upgrade process?
NutzShellsFriday, February 15, 2013 6:58:51 AM
Sad. Sad, just sad.
Sure, Webkit will improve over time, and I guess we won't lost Opera features and customizable UI. but Presto is the main charm of Opera. Period.
To be honest this decision is dangerously similar to Nokia's decision of ditching Symbian for Windows Phone. Symbian was a very mature OS with wide capabilities built-in, quite the same with Presto as a rendering engine.
See what happened to Nokia's Market share?
For the first time of my life, I'm thinking of changing my primary browser. This is coming from person who regularly use Fx & Chrome, even IE and Safari sometimes.
von Tetzchner was right to left Opera, he must have seen this coming.
ChirpieFriday, February 15, 2013 12:59:30 PM
Originally posted by NutzShells:
but Presto is the main charm of Opera
How? Most people have no idea what engine they are using. All they see is the GUI.
To be honest this decision is dangerously similar to Nokia's decision of ditching Symbian for Windows Phone.
Wrong.
Nokia ditched Symbian for an unproven OS with no support. Opera ditches Presto for one of the most popular browser engines.
This is more like Nokia moving to Android over Symbian. Or Apple using open-source components to build their (then) new Mac OS X.
Get a clue.
PengeFriday, February 15, 2013 1:30:53 PM
+1 question: What about the Fit-to-Width?
Yowan rdotexeFriday, February 15, 2013 2:44:42 PM
I personally think it's a good idea especially for web developers who won't have to use lines of codes to make their websites compatible with Opera. WebKit is the way to go.
NutzShellsSaturday, February 16, 2013 4:02:46 AM
Ah first come first, this is just my opinion, so feel free to disagree.
Originally posted by Chirpie:
Originally posted by NutzShells: but Presto is the main charm of Opera How? Most people have no idea what engine they are using.
LOL
Presto is a great little engine. It's small, fast, flexible and standards compliant while at the same time handling real-world web sites. It has allowed us to port Opera to just about any platform you can imagine
That's the main charm, Presto allows Opera web experience to be similar, smooth as butter no matter what is the platform. Mobile, Mini whatever Presto is behind them. Yes, you could argue Webkit is succesfully implemented on iPhone, Android, even Symbian s60 browser, but I personally still think Opera Mobile with Presto still blow them out of the water.
Originally posted by Chirpie:
Most people have no idea what engine they are using, All they see is the GUI.
That's the problem, most people *don't* use Opera. Opera's current user bases, IMHO are either technologically inclined and/or a die-hard UI fans. Since they choose to deal with incompability rather than simply switching browser. The latter perhaps won't care as much till this Webkit switch started to make their browser behaves differently.
Originally posted by Chirpie:
Wrong. Nokia ditched Symbian for an unproven OS with no support. Opera ditches Presto for one of the most popular browser engines.
Sigh, you're the one who should realy get a clue.
MSIE Trident was a very very popular browser engines with tons of support (putting aside the source-model and what platform it supported), I could also mention Gecko.
The point is more popular and supported doesn't necessarily means something is better. Hey, Firefox is more popular than Opera, and one can say it got a lot more of support in the interweb.
Well do you personally think Fx is better than Opera?
As for me, the issue isn't what engine will Opera be using in the future, the change itself is the issue. That's why I think Nokia's decision on ditching Symbian for any OS is very analogous to Opera's decision of ditching Presto. Good or bad, time will tell.
Benyamin LimantoSaturday, February 16, 2013 1:33:56 PM
Sadly, why opera leaving presto? maybe this thing same happend like when nokia leaving symbian, that will more worst for opera in mobile competition, ucweb have eat opera position. So i think opera must still develop the presto engine at all, i never let presto go! WE symbian user always support presto engine! Always untill the last blood we can do! Opera Presto is much light than webkit, in Symbian web kit have a bad rendering at all, i never getting error when using presto rendering in symbian.. Really hope.. this's Bad Decition... really
JimThursday, February 14, 2013 12:29:10 AM
Not to mention it hardlocks every computer I have tried it on if I browse like I do in Opera!
AGAThursday, February 14, 2013 4:22:44 AM
ОлександрThursday, February 14, 2013 11:19:58 AM
Old-NickThursday, February 14, 2013 12:43:03 PM
alexvodaThursday, February 14, 2013 1:06:33 PM
If the DECISION IS FINAL and IRREVERSIBLE PLEASE
If you are switching to Chromium, Webkit and V8 then Presto and Carakan would be considered abandoned, therefore you would no longer have any use for them. So donate what you no longer have a use for to the community.
Put them on github along with Dragonfly!
JTGbtThursday, February 14, 2013 3:10:07 PM
PengeThursday, February 14, 2013 5:08:48 PM
What will be the fate of Magic Variables after switch from Carakan to V8?
There are any alternatives in the V8 JS engine?
One more question: The structure of profile will change? For example converting INI-s to JSON, etc. which may cause problems in the upgrade process?
NutzShellsFriday, February 15, 2013 6:58:51 AM
Sure, Webkit will improve over time, and I guess we won't lost Opera features and customizable UI.
but Presto is the main charm of Opera. Period.
To be honest this decision is dangerously similar to Nokia's decision of ditching Symbian for Windows Phone. Symbian was a very mature OS with wide capabilities built-in, quite the same with Presto as a rendering engine.
See what happened to Nokia's Market share?
For the first time of my life, I'm thinking of changing my primary browser. This is coming from person who regularly use Fx & Chrome, even IE and Safari sometimes.
von Tetzchner was right to left Opera, he must have seen this coming.
ChirpieFriday, February 15, 2013 12:59:30 PM
Originally posted by NutzShells:
How? Most people have no idea what engine they are using. All they see is the GUI.Wrong.
Nokia ditched Symbian for an unproven OS with no support. Opera ditches Presto for one of the most popular browser engines.
This is more like Nokia moving to Android over Symbian. Or Apple using open-source components to build their (then) new Mac OS X.
Get a clue.
PengeFriday, February 15, 2013 1:30:53 PM
Yowan rdotexeFriday, February 15, 2013 2:44:42 PM
NutzShellsSaturday, February 16, 2013 4:02:46 AM
Originally posted by Chirpie:
LOL
That's the main charm, Presto allows Opera web experience to be similar, smooth as butter no matter what is the platform. Mobile, Mini whatever Presto is behind them. Yes, you could argue Webkit is succesfully implemented on iPhone, Android, even Symbian s60 browser, but I personally still think Opera Mobile with Presto still blow them out of the water.
Originally posted by Chirpie:
That's the problem, most people *don't* use Opera. Opera's current user bases, IMHO are either technologically inclined and/or a die-hard UI fans. Since they choose to deal with incompability rather than simply switching browser. The latter perhaps won't care as much till this Webkit switch started to make their browser behaves differently.
Originally posted by Chirpie:
Sigh, you're the one who should realy get a clue.
MSIE Trident was a very very popular browser engines with tons of support (putting aside the source-model and what platform it supported), I could also mention Gecko.
The point is more popular and supported doesn't necessarily means something is better. Hey, Firefox is more popular than Opera, and one can say it got a lot more of support in the interweb.
Well do you personally think Fx is better than Opera?
As for me, the issue isn't what engine will Opera be using in the future, the change itself is the issue. That's why I think Nokia's decision on ditching Symbian for any OS is very analogous to Opera's decision of ditching Presto. Good or bad, time will tell.
Benyamin LimantoSaturday, February 16, 2013 1:33:56 PM