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.
Permalink for comment 552334
To read all comments associated with this story, please click here.
Opera's user interface
by Dave_K on Wed 13th Feb 2013 16:34 UTC
Member since:

To me it was always the customisable and flexible user interface that made Opera special, not the engine. When it was competing with Netscape and IE5 it was particularly fast and light on resources, but that's no longer the case these days.

Unfortunately, a lot of my favourite Opera UI features have been broken, with options I've used since the days of Opera 3 or 4 not working correctly. I've tried the latest version and it still has a number of annoying UI bugs that were reported years ago. To me recent versions of Opera don't even come close to matching the browser it used to be.

Maybe without the engine taking up resources they'll put some effort into the UI? After all, that's the one thing left to set them apart from the other perfectly decent WebKit browsers...

If dropping the proprietary engine means that they'll finally fix the annoying bugs, and maybe even improve neglected features like Opera's dated session management, then I won't miss Presto one bit. I'm not going to hold my breath waiting for that to happen though.

Reply Score: 3