Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Opera Software De kogel is door de kerk: as we already talked about earlier, Opera is going to switch to the WebKit engine, leaving its own Presto rendering engine behind. We didn't yet know if they would the switch only on mobile or on the desktop as well, and they cleared that up too: both mobile and desktop Opera Browsers will switch to the WebKit rendering engine.
Thread beginning with comment 552385
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: RIP Opera
by PresentIt on Wed 13th Feb 2013 21:26 UTC in reply to "RE[2]: RIP Opera"
PresentIt
Member since:
2010-02-10

Yup, their JavaScript bugs alot and freeze Opera on certain pages. I open IE, use the same URL, works like a charm, go figure.

The reason for this is obvious. If they are hit by a performance bug in IE they'll fix it right away. Not so for Opera.

So even if Opera has fewer performance bugs than other browsers you won't notice it because sites will work around those bugs in other browsers, while leaving the ones affecting Opera alone.

I stopped reporting problems to Opera since they don't give a fuck about reports or you have to insist very heavily, massively (like the mouse gesture in 11.5 I guess) for them to step back with their "new advanced feature mania".

LOL, that's clueless. Opera has always added new features.

Opera has become the Fedora of browser : breaking what used to work, new bad functionning features pushed to users without them demanding for, all about hype.

How do you know if something was demanded or not? Just because you don't want it doesn't mean no one did.

Reply Parent Score: 4

RE[4]: RIP Opera
by Kochise on Thu 14th Feb 2013 08:23 in reply to "RE[3]: RIP Opera"
Kochise Member since:
2006-03-03

1- On the JavaScript problem, here 12.14, try this :

http://www.pagesjaunes.fr/
"Qui, quoi ?" = "Centre equestre"
"Où ?" = "Pau"
"Recherche à proximité de" = checked

Once on the result page, scroll down and hover the map.

2- Yup, Opera always added new features, in the beta first, then in the "stable" release. But it always have a drawback, you have to get it all, almost no way to disable this or that feature one by one.

3- If they push new features, it would be cool they are fully functional and don't requires a dozens updates to get them fixed. The "visual mouse gesture" fiasco introduced in 11.5 was a pure mess no one ever understood why they pushed it without warning :

http://my.opera.com/community/forums/topic.dml?id=839952

When I say I stopped reporting bugs, because it's always left open with no answer :

WebGL do not work : http://my.opera.com/community/forums/topic.dml?id=1593342

Nothing changed, yet it's advertised as a major compatibility point. Nope !

Mails gets scrambled after Opera crash : http://my.opera.com/community/forums/topic.dml?id=1438962

Never corrected, reseting the M2 client is still not possible without using tricks. And I don't speak about reimporting all the mails and mail accounts :

http://my.opera.com/community/forums/topic.dml?id=201905

Soooo, since Opera is always focusing on new features without maintainting their old features, I give up.

Kochise

Reply Parent Score: 2

RE[5]: RIP Opera
by PresentIt on Thu 14th Feb 2013 19:15 in reply to "RE[4]: RIP Opera"
PresentIt Member since:
2010-02-10

Wow, so there's an apparent JS problem in a browser. So what? What does this have to do with anything?

WebGL isn't even finished, HWA was disabled by default, and now we know why. They decided to switch to WebKit instead.

Mails get scrambled after a crash? No they don't. They work fine after a crash.

But what you are doing now is just to desperately try to change the subject by linking to random stuff. Anyone can link to random bugs in any browser.

Reply Parent Score: 3