Former Dev Gives Gloomy Outlook On Linux Support For the Opera Browser

An anonymous reader writes: "It doesn't take a Columbo to figure out that the 'previous employer, a small browser vendor that decided to abandon its own rendering engine and browser stack' is referring to Opera in this comment answering the question 'Do you actually use the product you are working on?' It appears to originate from Andreas Tolfsen, a former Opera developer who is now part of the Mozilla project. From releasing a unified architecture browser including Linux support since 2001, Opera decided to put Linux development on indefinite hold, communicated through blog comments, and focus on Windows and Mac for their browser rewrite centered around the Blink engine that had its first beta release last spring. The promise to bring back the Linux version in due time was met with growing skepticism as the months went by, and clear answers have been avoided in the developer blog. The uncertainty has spawned user projects such as Otter browser in an attempt to recreate the Opera UI in a free application. Tolfsen's statement seem to be in line with what users have suspected all along: Opera for Linux is not something for the near future."

For Those Who Forgot about Opera

[jazman_777]

Opera users typically were hardcore about it, and would only let go when you pried their cold dead hand away from it. I've been a longtime Opera user...the new version is derisively called "Chropera" and I've dumped it. It's just bad, so many of the things that made Opera are gone, so why use this Chropera? It didn't even have a bookmark manager, just that stupid Speed Dial. And then there is the general evasiveness of the devs, especially about a Linux version. So if you've forgotten about it, consider it a mercy. For those of us who loved using Opera, it's very painful.

Yup, an epic management coup.

[game kid]

Yup, this was a glorious coup by company higher-ups.

Grats, Opera management. You managed to kick out a good founder [slashdot.org], kick out a good engine [slashdot.org], and kick out any certainty that you won't be sold out to Facebook [slashdot.org] (Facebook, ffs!). You even made me wonder, between Tolfsen's account and the second engine change (from WebKit to Blink) [slashdot.org], if Google has simply stuffed your ranks with their management just to Elop the place.

ggwp.

Re:Opera is dead.

[theArtificial]

It's just a disfunctional Chrome with Opera branding now.

Chrome is just a dysfunctional Webkit, which is just a dysfunctional Khtml....

While losing Presto, which has been around since the early days [wikipedia.org], sucks it's not exactly cheap "me-tooing" the other guys. Besides, one of the reasons for the lack of popularity was the obscure rendering issues occasionally encountered with pages. "Whelp, my banking site just doesn't work, gotta switch browsers" type situations weren't exactly uncommon and arguably speak more about the markup than the engine itself but an end user might not be so understanding. Operas approach makes a lot of sense from a technical standpoint. One could dream about an opensource Presto but with the whole software patent blight I don't see that occurring any time soon.

It died when they abandoned their own codebase.

Seems more like a fork, doesn't it? Feature branch the engine, keep the UI. Granted it's still under heavy development, I'm excited about seeing it mature - I'd like to see how their development tools will be integrated (element inspection and whatnot) since the "old" Opera is known for having many useful features baked in. I'd like to see a webkit with some sweet extensible architecture so we might have Firefox level plugins, see Adblock. I realize this is available now but the effectiveness varies from Chrome to Firefox due to how webkit handles network requests, I'd like to think there is an opportunity here. If development time is ultimately saved as a result, hopefully additional features will once again be the focus instead of reinventing the wheel.