Tinsel Stars

Happy New Year from the Opera Desktop Team! With the best wishes for the new year to our community, you, and your near ones.

On the eve of the New Year, we will take a quick look back at the 60 releases we have had in 2013 since moving to the new release model:

  • 4 major Opera releases
  • 11 Opera maintenance releases
  • 27 Opera Next releases
  • 18 Opera Developer releases

We are very happy with having released this many updates in such a short time. We except to keep up the development speed and quality level in 2014. Thanks again for all the feedback and support we have gotten from all of you this year.

Get the Tinsel Stars theme by Opera to dress up your browser for winter. Find more winter themes.

Back to top
  • ahoj1234

    Happy new year to you guys as well 🙂


    High numbers that don’t correspond to what they should mean. 4 major release that look like -4 and most importantly from 15 to “19” there is no more than 1 minor release in terms of content.

    You can count 60 releases and that’s good, but they don’t feel like an improvement.
    Let’s see if we can actually obtain something by the end of this year (like Opera Link, bookmarks, other things I forgot because it’s late and I’m still using Opera 12 all the time except on the tablet where every time I run “Opera” Dev I see what I’d lost).

    It’s up to you for it to being a good year, you became a bad chrome clone from a disregarded wonderful browser (with its problems, sure). It’s up to you evolving in something better.

    • woj_tek

      This is sad. Very, very sad. It’s not even funny with ‘we have a gazzilion releases’ and yet hardly anything has changed/improved (yay, we finally have usable bookmarks… oh wait).

      On the other hand I’ve recently found out about Otter Browser (http://otter-browser.org/) – the aims seems to be to recreate Opera 12.x UI and funcionality – based on Qt5 and (currently) WebKit (but probably different engines in the future). This does look promising and actually for an alpha (actually not even alpha1) seems to have better prospects than this atrocity Chromera (sic!)… not to mention it’s developed currently by a single person – not the whole team.

      IMHO this is what the transition to chromium engine should look like – keep the ui and funcionality, change the engine…

      • II_ARROWS

        I agree, but how they told it changing the engine and maintaining the user interface was not possible, and that makes a lot of sense.
        If Presto was capable and used for interface rendering, they cannot just replace it with Webkit and keeping on.

        They had to address the interface before announcing a “stable” release, that’s for sure.

        • woj_tek

          OK, granted, but… what they actually produced doesn’t even remotely convey what Opera stood for. So they decoupled the UI from engine (presto) and throw us what? chromium and chromium like UI (despite it looking like chromium they say it’s native and so forth). Nevertheless it seems that the interface is stable enough but… now they claim that more and more features wont come back. So? A lil’ bit of fail here…

      • al_ghul

        you’re right Right RIGHT!!! change engine, keep functionality! that’s good path!

      • OperaIsDead

        So interesting!
        Let’s hope its development will be fast and good!

        I hate Chropera!

        Opera ASA killed the real Opera (version 12.16).

        • woj_tek

          It’s open source so the bigger the interest and contribution the stronger the project is 🙂

      • happy

        It’s amazing that bookmarks had to be pried out of them kicking and screaming all the way. Finally they relented a little, but it was like, okay yeah there are a few random dumbasses out there that use bookmarks, so we will include some basic bare-bones bookmark functionality for the few very very few random dumbass computer-illiterates that use bookmarks. Yeah thanks a lot Opera.

  • Strathos

    Thanks, Opera Team! It’s been a year of transition and new prospects. I think Opera is in the right track to take in what the web is shaping to be and I’m very excited about further development.

    Happy New Year! May it be a prosperous one!

  • TwistedAndy

    60 releases – it’s really big number, but what was really changed? Where is normal bookmarks system? Where is Opera Dragonfly? Even such obvious feature as showing full url in address bar is still absent. Is it really hard to implement? Maybe, it will sounds strange but now the Chromium is much usable than new Opera with 60 releases.

    • al_ghul

      yeah, I agree with the last line – making new opera usability equal (in first run) to chrome should be a good move – chrome is a good, natural standard and base for any modern browser, opera especially.

      • Lovestospooge

        “Chrome is a good, natural standard” made me chuckle a little. Then “and base for any modern browser” made me lose it completely.
        Those statements *might* have been true two or three years ago. Right now, Chrome is nothing more than the Internet Explorer of the 2010’s.

        By basing themselves on Chrome, Opera lost every single advantage it still had over the other browsers, and gained every issue Chrome has: from the terrible settings manager to the severe unstability of the engine, and let’s not forget the rigidity of a very limited, not completely functional interface – that second part being about the tabs.

        Making a Webkit-based browser ? Sure, why not.
        Making a Chromium-based browser ? Seriously what’s wrong with you guys…

        How hard was it to make your own thing out of Webkit and V8 ? Not very hard I believe. Not nearly as hard as it will be to sell bullcrap like Opera 13+.

        • al_ghul

          I disagree. chrome first of all – is fast and quite good in displaying modern, google-like sites. so IMO it fits better in modern browsing. even if other arguments may classify it low. browser for me mainly has to be fast and correct in displaying sites. it’s in my opinion base of quite good site browsing. of course, chrome may have some cons, which I can or cannot understand, but these ones are not so much important to me. well, in fact I used many years opera, until 12, and now opera 18 and later works faster and more stable than older one. of course, 12 has much more options and customisation, but lost essentiality – fastness and correct browsing modern sites. i hate simplicity of new opera, but pros of it are greater than cons…;P and engine is only engine, it can be expanded and rebuild old opera featues. it’s matter of time and developers needs…well i may agree with you only in the matter of engine webkit or chromium…maybe they should go to more open webkit…

          • Lovestospooge

            It does display modern sites much better. And it’s most of the time faster. My problem is that it’s fairly unstable… other browser crashes too, but not with such a systematic fashion.

            Using different processes for each tab also seemed like a good idea… at first. As it turns out, the disadvantages are not worth a few less global crashes of the browser. It’s doesn’t make it anything faster (maybe Chrome would be even faster without that), and it takes a shitload of ram.

            And though they can re-implement some features, they have to keep the Chromium basis now. They are so limited and guided in their further developments that it’s fairly sure they will never re-implement most of Opera’s greatest features.
            In the new Opera, here is a list of things you will most likely never see again: dragonfly, stacked tabs, tab preview, wand, no-reloading back/next buttons, a simple way of setting a speed dial background image, clear, compact and usable interfaces for settings, history and downloads… things that they’ll never spend time on, because it’s not worth the money.

            In a way, this is all a good thing, because it brought Otter Browser to life. And being open-source and Qt-based are the two things Opera 11 needed to keep up the good work.

          • al_ghul

            well I agree that most of functionality of old opera won’;t be reimplemented…but IMO average user of old opera didn’t need all of them. but I hope that they don’t make opera another chromium-based browser with the same capabilities. imo all these features you mentioned can be implemented if developers want it. chromium/blink is an engine wchich can be elaborated more or less. i think they take chromium because it has the basic capabilities of modern browser and google dominates in web applications. well, about stability i cannot say anything – in my use chrome and opera works more stable than old opera. of course, engine always limit capability of development, but I think they wanted working modern engine, so take open source chromium.maybe they don’t reimplement all features, because they want get also not-advanced users which want fast browser. they change target I think, but I hope don’t forget at all old users which love old opera. generally I don’t like the direction of new opera, but maybe they have to do it, simple because of economics – they have to change engine to render modern sites, google blocked old opera in their sites. they had to change…and from the other site – maybe programmers also wanted to go in different direction – more modern trends – simplicity – also ff change directions and “simulates” chrome look. i also changed old opera because of slower work and sometimes lack of stability, especially in google-like sites. new opera, although it lack more opera functionality, still is faster and more stable than old, so I work on the new version…and hope they reimplement old things asap…

          • Lovestospooge

            Well… the tab stack is such a hard and delicate thing to implement I’m pretty sure they’ll never implement it again. Hell, I even doubt Otter will manage to do it (despite it being in their todo-list… they’ll have to re-write a shitload – if not all – of tab bar and tab preview code).

            And yeah… god damn google used to block Opera. They’ve been putting pressure on them for a while, it makes a lot of sense that Presto would eventually be dropped in favor of something Webkit or Blink based, something that Google cannot pick on.

            However I think the move from Opera to Chropera is less motivated by the quality of display and the speed than it is by purely economical reason.
            My point being that it was certainly very possible to port the current Opera to Blink. But that it was impossible to do both that and fire most of their development staff.
            So they found a solution that required a lot less manpower and fired a lot of their developers. Maybe they didn’t have a choice, but well… that’s disapointing.

            I’m not against Blink software-wise: just against the crap that Google built around it to make Chromium.
            And moral-wise, for the past few years, nothing that came out of Google was morally acceptable.

            Blink is nothing more than Google’s way of gaining and abusing all the privileges Internet Explorer had in the past decades… the same way Internet Explorer gained and abused them. And that’s a bit terrifying too.

          • al_ghul

            well, maybe hey don’t reimplement tab stack…to be frank – I didn’t used them, although I’m used to have open tens and more “to see later” tabs (now i have 26;P). do you mean that separate processes of each tab won’t make it possible? well, i think programmers and developers are not only changing parameters in code, but also built new ones;).

            you mean that webkit cannot be “blocked by google” as presto was?

            well I don’t deny that economics may was the key…opera is small company, so I think they needed quite ready browser engine, not application language…of course there is cons and pros of every choice. yeah, I agree. manpower was also the point…

            well about google practices – it seems the same as with other companies as e.g. MS etc. – monopolism often leads to bad practices, I also don;t like them, but I think there are alternatives and one can use only several apps from google, not joining all to g+.

            well, it is such similarity, but chromium/blink is open project, more or less can be changed/forked. see how many browser based on chromium was developed…

            it’s a bit astonishing, I have also objectioins, but not so much terryfied;)

          • modern, google-like sites? what is that crap now?

          • Lovestospooge

            The kind of crap à-la Google+ that Google has been using to update its other apps recently, from Drive to Mail. A lot of sites also have modern interfaces as advanced as those of Google, but some of these sites seems to optimize only for Chrome. GMail and Google+ are terribly slow when used from Opera 12.

          • al_ghul

            yeah i agree, and that’s why I use chrome or other clones like opera;P. of course maybe building all sites on JS is bad practice, but from good web browser I expect fast and correct browsing, if JS is evil, but u cannot change practices of all programmers (u are only opera developer;P)- u must workaround it – change something. it’s something like when old opera in the past best matched html/w3c restrictions, but all programmers built sites mainly for IE or FF.

          • Lovestospooge

            It’s not as much Javascript as… something they do. Don’t know what.

            I’ve been web developer for a while, I used and even developed many similar interfaces that just work on Opera.

            Bootstrap for instance is a very popular CSS/JS toolkit that works very well with the old Opera. And anything you can do in a Google+ interface, you can do with Bootstrap too: and best of all you’ll see the difference in responsiveness with every web browser.

            And about the progressive disappearance of Javascript, I suppose it’s about CSS3… I hadn’t seen it that way but come to think about it it’s true: the most expensive stuff we do with Javascript is what CSS3 will allow us to create in a more… appropriate fashion. Javascript won’t disappear, but it’s very likely that the amount of code run will drastically diminish.

            Which wouldn’t have helped Opera anyway, because Javascript isn’t really what made Opera slower: imo their rendering engine simply wasn’t optimized for the way the applications were written. Plus anything involving transformations was pretty slow.

          • al_ghul

            maybe You are right with site rendering, I didn’t take it into account…it’s also possible. yeah, I remember times when old opera was the fastest browser in js…

          • al_ghul

            I mean all these sites with some buttons/actions/pull down menus similar to google services such as gmail, google+ etc. and horizontal sites, all of them in which old opera worked very slow and unstable.

          • Vux777

            main Presto flaw was poor JavaScript performance, and all those sites use JS more and more…and that thing will just grow (JS usage)

          • Guest

            yeah, I supposed that is JS, I recently found that JS is mainly responsible of this..

          • al_ghul

            yes, I found recently that it’s caused mainly by JS…well, i heard also that JS will be used less and less in modern sites, like flash…but it seems opposite;P

  • Vux777

    Happy New Year to you guys, too!

  • Babua Sheni

    i hope 2014 will be better for opera than 2013… right now opera is disgusting for me…

  • Tüütlüm Ohaya

    Happy new year Opera Software (:

  • Łukasz Darzki

    “4 major Opera releases
    11 Opera maintenance releases
    27 Opera Next releases
    18 Opera Developer releases”

    And not a single feature that chrome does not have. What a great year, great year.

    • Davit Babayan

      Mouse gestures

      Speed Dial with extensions
      Opera Turbo

  • Davit Babayan

    Happy new year for all Opera developers and fans !

  • UMaster 7

    Happy New Year. And don’t forget to continue the work on Opera Mail 😉

  • 0.o

    When will the next updates come? You working already? 🙂 As the gif-bug gets fixed i can use Opera again 🙂 Also i might have spotted a new bug, i’m still trying to reproduce it, some problem between Opera and xajax

  • Igor Tarasov

    And 0 Linux Opera releases.

    • cfastner

      I second Igor’s comment . . . whatever happened to Opera’s support of Linux??

    • RonaldoTT

      I also want to use the new version of Opera on Linux. Because this is not yet possible, I have written a poem. I hope that my poetry is the inspiration needed for a Linux version of New Opera.

      My Desire for New Opera for Linux
      A Poem By RonaldoTT

      New Opera for Windows and OS X, you are so shiny and new!
      New Opera for Linux, I search and I seek, but I cannot find you!
      I desire your presence; I want you so bad; I desire your being.
      For it is the web with New Opera that I do wish to be seeing!

      Every morning I wake, my body lusting with a burning desire;
      To open New Opera on Linux, and browse the web without tire!
      But the pain I soon feel;
      ’tis very much real.

      Alas, there is no New Opera for Linux, I am afraid to say.
      And for this lack of New Opera for Linux, a deep hurt I must pay.
      This lack of New Opera for Linux puts me in panics!
      Please, Opera, please release New Opera for Linux!

      — RonaldoTT

    • NightMayor

      Which absolutely makes no sense since both the Chromium Browser and Google Chrome use the Blink engine but have released updated browsers on Linux. I’m wondering what features (or bugs) is keeping Opera from Linux.

      • al_ghul

        a manpower?;P

    • Raylan Givens

      Let’s stabilize the Win version with the basic features and forget Linux for a while. Even the Win version lacks the most fundamental features or don’t work or semi-work.

  • Wibby

    Looking forward to the next developer update, CSS transistions and GIFs have been working sob-optimally.

  • vinczej

    Happy New Year, developer guys!

  • Leonardo Gomes

    Happy New Year.

  • LOL: Happy New year is only for happy people. The whiners are still moaning about no Linux version yet, no bookmarks, etc., just like last year. So what’s new?

    Never mind the whining. Just continue working patiently.

    “When fleeing the chasing tiger, never mind the barking of dogs.”


      There are substantial differences between complaining and whining.

      • Yes, complaints have a substantive basis, while whining does not.

        “The QAB doesn’t support searching for bookmarks” would be a legitimate complaint, “the QAB is not bookmarks,” or “the QAB is useless” is just whining.

        • II_ARROWS

          And people keep explaining why that QAB is stupid, for many reasons: horizontal space is unusable and you cannot open folder, vertical space is wasted, horizontal space is unused in wide screens…

          People are not whining, at worst people are tired of writing the same basic thing over and over and then they just remember the topic.
          I only see whining about “whiners” because I don’t see anyone giving a constructive speech about this, especially from Opera’s employee that should just do that.

          • Writing the same thing over and over is whining. Calling the QAB “stupid” is whining. Claiming that it has “zero functionality” is ridiculous.

          • II_ARROWS

            You are trolling and/or whining.

            I explained, you just pointed your finger and whined. That’s the difference between me and you.

        • Alaknár

          No bookmark nicknames, no folder nicknames, no bookmarks manager, etc.

          Calling QAB in it’s current state “crap” is a legitimate complaint since it has zero functionality of the Opera 12.x system. I could put bookmarks on the desktop and set Opera as the default browser and have better functionality than QAB…

          It also feels ‘detached’ from the rest of the browser. Once a bookmar gets to the QAB, it’s there. You can delete it or rename it and that’s it. Want to move it to the Speed Dial? You need to insert it there manually, can’t drag and drop.

    • Couldn’t agree more.

    • Popiel

      People are complaining and criticizing a weak, joke-like product called Opium 15+… But there are a few whiners like this Pesala, who can’t stand it and bark in their whining style on every critic they see.

      How pitiful is a guy who spends all his time whining about perceived “whining” of others.. And he claims to practice Buddhist virtues…lol…
      The guy can’t stand any critic of something else, so how would he stand a critic of himself.. Certainly he is not a talented Buddhist..

      • The glass-half-empty people can only see the faults of the New Opera. The glass-half-full people can also see the faults, but they appreciate the hard work done by the developers, and wish them well for the New Year.

        It’s hard to work effectively when good efforts are undervalued, and people only criticise what is not done, or not done very well yet.

        The whiners have never developed anything except ill-will. They are lazy bums who do nothing to help others. It’s easy to spot them on the forums — maybe just one post, or a few dozen at most. They are too busy playing games on Facebook or chatting with the other twits on Twitter to do any real beta testing or make any useful suggestions.

        Those of us with 10,000+ forum posts who have been helping others for years have seen and heard it all before. Every new release brings the whiners out of the woodwork to point out the obvious for the 100th time.

        When we criticise them for whining they have nothing better to do than make personal attacks.

        The developers can safely ignore such people — they do nothing to support the Opera Community.

  • iemand

    I actually hardly miss the ‘old’ bookmark method. I now always use speeddial and stash for like forum topics that are just ‘hot’ for a short period of time. Also at work it’s a nice addition. I used to use Firefox for CMS content writing and now Opera has gone to Chrome engine it works fine in Opera (like a lot of banking stuff)..
    Tried Chrome but the privacy aspect worries me. Chromium based Iron was irritating to update and I was also a bit worried for privacy.
    Also kudo’s on the discover feature, it works great for Belgian/Dutch news (unlike a lot of other services that only have English sources).

    Only things I miss in this Opera are master password (sometimes I leave my PC unattended and don’t like the idea people can just see my saved passwords without any form of security), sync and an Opera app for Win 8.1 (although IE11 app is – to my surprise – quite nice).

    • oic

      I think ppl are missing the point of the old bookmark system. Its not just the bookmark, its the bookmark manager. Its easy to sort. Speedial and stash is still very hard to sort. At least upgrade speedial with more features like, sorting in list form, folder, alphatibetically order. Make it easier to move bulk bookmark from one folder to another

      • al_ghul

        agree with both of you://

      • II_ARROWS

        You cannot keep QAB folders and speed dial open all the time, and both are wasting space (one more than the other).
        Speed dial is a good idea and implementation, but it’s not a replacement for bookmarks, it’s a completely different world and purpose.
        The QAB is hard to navigate and a complete waste of space.

        It’s not about managing bookmarks, when I save a new bookmark I won’t change it’s position (maybe I’ll just delete it), because I’ve already put it in the right folder.

  • The Solutor

    Happy new year.

    2014 starts with a little hope from an unespected direction.


    Looks like there is still intelligent life on the earth

    • DD64

      For some reason I think, this will be really, really great.

    • al_ghul

      and this is the right direction, still very original to other browsers (although there is opera 12)…only if developers of the new opera would like to follow these (in real – their own) footsteps…

    • The Solutor

      For your convenience, ATM, one of the places to interact with Otter’s developer is here.


    • Lovestospooge

      You mean a browser based on what works in Chromium, but not in what fucks up ? Lord, however did anyone came up with such an idea ? Must be a genius: even people paid by Opera Software weren’t able to have it.

    • ayespy

      Hm. Looks interesting, I guess, but until there is a windows installer, one will need to be a technical genius to take it for a test drive…

      • DD64

        You just have to extract the zip-file and start otter-browser.exe

      • Vux777

        I downloaded 35 MB alpha pack …worked as expected…very early alpha

        • ayespy

          when I get some time, I’ll have to try that.

        • al_ghul

          yeah, project is still VERY raw and spill of errors sometimes, but it’s promising because of project’s idea – revival of old opera:)

      • The Solutor

        I have just unpacked it, and clicked on the executable.

      • Lovestospooge

        You don’t need to be a technical genius to even compile it. It’s very straightforward:
        – Download Qt 5.2 with QtCreator
        – Go to the git-hub repository and click the “Download Zip” button
        – Extract the archive you just downloaded
        – Open the CMakeList.txt file using QtCreator. A wizard will guide you through the step (basically you just have to click next and at some point “execute cmake”).
        – Click on the big green arrow on the bottom left of QtCreator’s interface

        You now know how to compile any Qt project (as long as they don’t have any other dependencies than Qt, which is the case for Otter).
        Regular Qt projects will have a name-of-the-project.pro file instead of a CMakeList.txt (CMake is just a more portable way of handling your projects).

        • Carlos Gómez

          Very useful information. I was googling to find out how to compile Qt projects on Windows, but it would have taken me a while since it’s always harder if one doesn’t know where to start. You saved me that time, thanks a lot.

        • ayespy

          Thanks. I don’t need to be taking time out for a new technical skill right now, even a minor one, if it doesn’t immediately contribute something to my work.

          Still, that’s a simple new bit of knowledge, and I will file it away.

          For the time being, I downloaded the package and extracted it, and can run the .exe from the extracted folder, so I have seen what the current development state of the project is – and already, it is in some ways more flexible than Opera. I eagerly await developments.

    • Hope it absorbs every whinner here.

    • Emil Huber

      And now everyone who miss the things from Opera 12 will leave us… And nobody will ever write posts like: “Opera 12 was the best browser in the world” or “Opera 15+ is the worst browser in the world”…
      Opera has changed its mind and has created a new browser. Here it is. If you like it stay here, if you do not like it then go to otter-browser. But please do not write thousands of posts about Opera 12.

    • guest6768

      This is ******** great !!! Thanks for the heads up.

  • Kartofel

    “4 major Opera releases
    11 Opera maintenance releases
    27 Opera Next releases
    18 Opera Developer releases”

    And not even one usable browser…

  • ayespy

    Happy new year!!

  • Princess Serenity

    Why Linux still 12.15 ?

    • Leonardo Gomes

      If i’m not mistaken, there is 12.16.

  • oic

    Are you trolling us with this news blog post? Not much has really changed
    60 releases but still no bookmark manager

  • Maggus

    Happy New Year 🙂
    The most important feature to add in 2014 asap: Bookmarks and Opera Link! Thanks 😀

    • Nekomajin42

      Sync is working in v19, so you will get it in 1-2 weeks.

      • Maggus

        Nope, I’m on v20 and nothing will update in Link if I add an bookmark!

        • Leonardo Gomes

          Because Link is for Opera Presto, at least on this monent. Opera Blink uses Sync, which will have a new web interface and will sync different things.

          • Maggus

            You mean Google Sync, right?

          • Leonardo Gomes


          • Maggus

            Hmm, ok… No matter what it is, Opera has to hurry up!

        • Nekomajin42

          Currently speed dial and stash items, and custom search engines are synchronized. Bookmarks, login data, extensions, open tabs and maybe others will be added later.
          And the Link is the old system which works only with Presto-based builds. The Chromium-based builds use Sync, which is not just a new name of the same service. They run entirely separately. When you first log into the Sync servers, it will fetch some of your data from Link, but that happens only once.

          • Maggus

            Sorry, but there is no “Sync” in v20… Only an link “syncronize” which link me to “opera link”! whatever, CoolNovo is for me the better browser than Chropera 😛

      • II_ARROWS

        If it’s working, they’d better do a better job on user interface (duh!) because I didn’t find it…

        • Nekomajin42

          Some kind of web UI will be available later. The last time, one of the devs said that the design was ready, but they had to write the backend. It was 3-4 weeks ago.

  • L33t4opera

    Thanks for the wishes 🙂
    Fill your heart with new hopes, reach out for new opportunities, and celebrate the New Year. Raise a toast, rock the dance floor.
    I wish you all a Happy New Year 2014 😉

  • 0.o

    How is WebGL in Opera? Does Opera support it? At least Chromium does.

    • Vux777

      Open opera://flags (experiments), search for WebGL and enable it…
      actually, clicking “enable” button will disable WebGL, because command is “disable WebGL”
      confusing ๏̯͡๏
      It should be ON by default (in O19 next is)

      ps. geek who made that kind of toggling flags logic should be shot in the knee…or foot

    • Leonardo Gomes

      Yes, Opera supports WebGL.

  • Gerard

    The last good Opera was 12.14. Since then I’ve only seen bad Chrome copies. Opera used to be on the top until it showed finger to its users in hope to chase crowds…

  • guest6768

    60 releases… A year of pure dissapointment!

  • RX-3200

    please close Next at all in 2014
    and make it 27 releases in maintenance and in Developer

    • Leonardo Gomes

      And for what reason they should do that?

      • RX-3200

        scheme with only one development branch worked for them for years – up to version 14 they had only one branch development and browser developed rapidly, and now it develops twice slower

        to branch Next they spent as many as 27 builds – it’s actually half of all builds for the year – and these 27 nobody wanted – they do not add anything new

        if they did not spend time on them – they were able to go back and/or add more relevant functions, and maybe then the old-Opera users come back to them

        • Leonardo Gomes

          Well, Opera Presto also had three development stages: snapshots/alphas > Betas -> Finals, not mentioning Betas and Finals Release Candidates. The only difference is that they weren’t too “separate” as today.

          Removing the Next stream would change nothing about the inclusion of new features, because when the version was considered “feature frozen”, nothing new would be added no matter how many builds were released until the final.

          You may not want Next builds, some people may also not want, but many others want them. Not everyone wants to use alpha stage builds just because of new features, there are lot sof people that wants to test/use those new features on a more stable build.

          Also, both Developer and Next stream are developed together, so removing one would not help the other.

          Btw, Opera development today is clearly more rapid and healthy than it was before.

          • RX-3200

            Do not confuse the stage of development and the development branch
            Now using Developer – you will never can to auto-upgrade to Next – is the development branches
            but in Presto we quietly updated to RC – and it was all one development branch
            and if you use Opera long enough – you have to understand why there is not even mentioned Final builds

            now for only using Developer, at the time of release branches Next – Opera freezes development – Next builds for them at all does not actually exist – for them for the year Opera has released only 18 builds !
            and 18 builds per year – it’s not 60, and about any “more rapid” – wrong speech

            in fact – almost all Developer builds so stable (except the last of 2013)
            and for those who need a stable straight stability – there is always a line Stable/Final
            Since you are using a developer – you have to agree that 18 builds per year – this is clearly not enough …

          • Leonardo Gomes

            I’m not confusing as they are basically the same, just more clearly separated now.

            Ah, in Presto time the snapshots were released as Opera Next that normally didn’t autoupdate to finals, sometimes not even betas. So we can say that there was two development branches.

            It seems that you are paying too much attention on versions numbers when, imho, you should focus more on the development streams.
            When a new major Next version is released, there is no development freezing on the Developers stream and you get a new version a couple of days late, at most a week later.

            About the numbers, they are not per year, but since the new release model has started. So there was 60 releases since july which is ~10 releases per month, ~2 realeases per week.

            And the Developer strem has started later so it’s obvious that its numbers will be lower than the Next stream.

            Imho people should not follow version numbers but a development stream.

          • RX-3200

            even so, you are confusing
            usually nobody uses two different new Operas at the same time – uses either Next or Developer

            now new Next & Developer not self-update to Stable – and now we have 3 (three) branches of development,

            but we’re not talking about Final – it is intended for a separate category of people – it does not actually interesting for us at all in Opera

            It seems that Google is bad translates my thoughts into English for you – speech does not go on version numbers,
            we have just about the amount of builds

            developers get only 18 bilds in Developer branch
            you must forget about Next branch to understand this

            it’s only one release per week – it’s at least two times slower than before in Presto

            and if someone use only Next – they have only one bild per week, and it’s at least two times slower than before in Presto too

            by closing Next branch we could return two+ bilds per week again

          • Leonardo Gomes

            I know that people usually follows version numbers, starting with Developer, passing by Next and reaching Stable, and i never said anything on the contrary. What i was saying was that in my opinion people should not do that but follow development streams instead.
            So based on how much bugs and instability you allow yourself to face, you should choose Developer, Next or Stable.

            Closing the Next stream doesn’t means that Developer stream would have more builds per week or even more builds in general. It could happen or not.

            Btw, Developers stream started on august 8th with Opera 17 whilw Next one started on June 24th with Opera 15. If they had started at the same time, they probably would have a very similar number of builds.

          • RX-3200

            and what for you write these things here? – they not relate to the “closing Next or not”

            you still do not want to understand
            closing Next – shorten the development cycle:
            instead of Dev-Next-Stable will be Dev-Stable

            three branches of the development here is too much for Opera – they simply can not afford it, and statistics show quite clearly that

            actually: if the proportion of Dev / Next would be 27/18 – it would be more appropriate, but it’s 18/27 – and it looks abysmally

            and in general: at this stage, until Opera missing many features that are standard in modern browsers, so At least until they are restored – the development cycle of three branches – it is too long

          • Leonardo Gomes

            “you still do not want to understandclosing Next – shorten the development cycle:
            instead of Dev-Next-Stable will be Dev-Stable”

            And how can you be so sure about that?

            It probably would have (almost) the same amount of builds and take the same amount of time for a Stable version to be released.

            “three branches of the development here is too much for Opera – they simply can not afford it, and statistics show quite clearly that”

            Sorry but i think you are wrong.

            There is nothing that could indicate that they are not being able to handle the three development stream system. on the contrary, all of them are doing very well and fast.

            The avarage number of builds per week is almost the same than the ones in Presto time and major final/stable versions are being released faster.

            “actually: if the proportion of Dev / Next would be 27/18 – it would be more appropriate, but it’s 18/27 – and it looks abysmally”

            You know that Developer stream started about two months (and two versions) later than the Next stream, right?

            As i said, if they would have started at the same time, they probably would have the same amount of builds.

            Closing the Next stream would not make the development faster nor would make more features to be added in a new version.

          • RX-3200

            the more we are in dialogue – the more the feeling that you do not understand what a “fast”

            look at other browsers with three branches of development
            eg FF – Nightly they release every night – it’s realy fast
            and release of beta and finals does not take them out for a week – so they have three real development branch

            at Opera, we see three virtual development branches,
            actualy they have only one branch, and while they are engaged in one of the Stable / Next / Dev – the other two stand waiting for their turn
            so there is no doubt that closing branch Next – accelerate the process

          • Leonardo Gomes

            “the more we are in dialogue – the more the feeling that you do not understand what a “fast””

            Nope, i know what fast means. The problem seems to be that our concepts of “fast” are clearly not the same.

            Also, Opera’s “fast release cycle” doesn’t mean that we will have more builds per day/week/month/year/whatever but that, i.e, people will not have to wait six months for a new feature and/or a bugfix that was ready six months earlier.

            “look at other browsers with three branches of developmenteg FF – Nightly they release every night – it’s realy fast
            and release of beta and finals does not take them out for a week – so they have three real development branch”

            Well, Opera doesn’t have nightlies (not public ones at least) so this comparison sounds nonsense to me.

            “at Opera, we see three virtual development branches,actualy they have only one branch, and while they are engaged in one of the Stable / Next / Dev – the other two stand waiting for their turn”

            Nope, it doesn’t happen that way.

            “so there is no doubt that closing branch Next – accelerate the process”

            Well, maybe for you. For me there is no evidence that closing Next would bring any benefits.

          • RX-3200

            from you one continuous unsubstantiated disagreement
            your explanations are ridiculous and do not stand up to scrutiny – you trolling me?

            The term “fast” is in the dictionary, and it is all the same
            then shown that “fast” – is one or several builds per day, and in response you start to talk about the kinds of builds – as we call it?

            Opera’s “fast release cycle” – does not really mean anything – it’s just a marketing
            because in reality this development cycle produces one branch builds (Dev OR Next) two times slower simply because the two branches instead one
            and error correction here at anything – Fix corrupting large images and displaing animated gif’s – we wait very long

            your “nonsense” and your “doesn’t happen” means only that you prefer not to understand what it is about again and again

            please do not write here more unsubstantiated things

          • Leonardo Gomes

            “from you one continuous unsubstantiated disagreementyour explanations are ridiculous and do not stand up to scrutiny – you trolling me?”

            You ar ethe one who started attacking and i’m the troll?

            Sorry but your attitude is typical of the ones that can’t admit th elost an dthen start attacking the others.

            “The term “fast” is in the dictionary, and it is all the samethen shown that “fast” – is one or several builds per day, and in response you start to talk about the kinds of builds – as we call it?”

            “Fast” is relative and always will be as It depends on the point of view.

            You seem to link fast development to the number of builds released and i don’t agree with that. More builds doesn’t necessarily means a faster development.

            You also seem to think that closing the Next stream would make the release of stable versions faster and/or that it would have more features added and i disagree with that too.

            “because in reality this development cycle produces one branch builds (Dev OR Next) two times slower simply because the two branches instead oneand error correction here at anything – Fix corrupting large images and displaing animated gif’s – we wait very long”

            Well, for you things may be slower but for me and for many others, they aren’t.

            The release of a specific bugfix has no relation to fast or slow developoment. Some bugs are fixed more quicker and some others take more time to be fixed.

            Even if we don’t have the Next stream, even if more builds were released, it doesn’t means that a specific bug would be solved faster.

            “your “nonsense” and your “doesn’t happen” means only that you prefer not to understand what it is about again and again or trolling ?”

            They mean what they mean: that it doesn’t make sense to include nightlies now in the debate and that what you’ve said doesn’t happen.

            “please do not write here more unsubstantiated things and other flood”

            The same for you. 🙂

            Anyway, since this debate is nothing going anywhere as it seems that ours opinions will never be the same, i’m ending my participation at the moment.

          • RX-3200

            “You seem to link fast development to the number of builds released and i don’t agree with that. More builds doesn’t necessarily means a faster development.”

            Reality shows us that one build now contains the minimum number of changes
            respectively: the more builds – the more changes

            more you keep silent about why you think so and not otherwise

            OK, time is subjective for each of their, but the numbers there is numbers
            for example: 18 used builds vs. 27 (or more) unused builds

            and you do not call it Nightly – you compare the power required to produce a certain number of builds
            see also my answer above

          • Leonardo Gomes

            Ok, this will be my last participation on this topic because, keeping a discussion that is leading to nowhere is just an unuseful waist of time and energy.

            “Reality shows us that one build now contains the minimum number of changesrespectively: the more builds – the more changes”

            Maybe but not necessarily. And there isn’t much difference from today to the Presto times.

            “OK, time is subjective for each of their, but the numbers there is numbersfor example: 18 used builds vs. 27 (or more) unused builds”

            27 builds starting from june against 18 builds starting from august. do you get it?

            Next only has more builds because that stream/branch has started about two months before.

            And those 27 Next builds being unuseful is just your opinion. Many people here think they are useful.

            “and you do not call it Nightly – you compare the power required to produce a certain number of builds”

            And what would be thi spower?

            You know that when a build is released to the public it was already tested before internally and by the “testers”, right? And that the next candidate to be a public release is already being tested?

          • Leonardo Gomes

            Just listing some points and i’m off.

            – Closing the Next stream/branch doesn’t means that the development speed would be faster.
            Instead of, let’s say, 4 Developer builds, 5 Next builds and then the stable one for Opera XX, we probably would have 9 Developer builds and then the stable build for the same Opera XX.

            – You could say that it would happen in a shorter period of time but you can’t be (so) sure. It could happen or not.

            – Closing the Next stream not necessarily would make features to be included faster neither it would make more features to be added on a specific version of Opera

          • RX-3200

            Since you yourself concluded that closing branches Next will not change anything – then nothing prevents her close

          • Leonardo Gomes

            Thanks for showing everyone that you were only trolling.

          • RX-3200

            No – you say no truth

            I seriously propose to close Next at all in 2014
            and make all it releases in Developer
            and all the reasons you were given

            and my previous comment to you was so because the inadequacy of your answers to the topic under discussion has gone too far
            yes, closing an entire development branch obviously can not leave everything as is

            My assumptions are based on how developed the Opera Presto
            your assumptions are not based on any facts and ignore the reality of the situation
            and why do you not then troll? – Why do you ascribe to me your merits?

          • Leonardo Gomes

            Just let me say one thing (or maybe two):

            I’ve been using Opera since even before Presto has been created; I’ve been using Opera since even before this blogs or My Opera exists; I’ve been using Opera since it was kida of the “browser (for geeks) that fits in a floppy disk”. And i’ve been following Opera’s development since the times when people discussed about the browser in a mailing list and/or on the newsgroups.

            So i think i have enough knowledge about Opera and its development and my assumptions are, mostly but not only, based on it and on commom sense.

            You, on the other hand, seems to have based your idea on some presuppositions that may not be necessarily true.

            But whatever, i will not discuss it anymore, If you want to keep spreading your ideia, go ahead. I still think it doesn’t make any sense for the reasons i’ve listed before.

          • RX-3200

            here does not matter your knowledge
            here it is only important that you pay attention to something, and something is not

          • RX-3200

            27 (or more) – is not 27 bilds, it’s nearly 42 bilds
            so realy it reading like: 18 vs. ~42

            “And what would be thi spower?”
            you have not seen the post above – are perfectly clear about what it

            “You know” – you really believe that? – Then answer the question yourself: why you mentioned testers are blind those bugs that we see in their allegedly tested builds?
            (and it’s not about the known issues)

          • Pedro Costa

            Sorry RX-3200, I’m a programmer myself and you are wrong. Fast Developement cycle is the time from development to stable (final) and Opera is on par with chrome and FF in that state. Example: The time it takes to get Dev 20 into Final 20.

            Nightly builds on FF are meant to be really buggy, because the testers are, mostly, the community, it’s an OS project.
            Whereas Opera has it’s own internal QA testers that, for sure, try daily builds. So what you receive for testing in the dev stream is something more stable than the nightly builds of FF, most of the time.

            Internally they should have a team for Dev and Next. People working on new features and people on ironing things up. When Next gets stable enough they say it’s a stable release. So there isn’t a Team for Stable! Just 2 stages! Besides, this 2 stages work is maintained at the same time. So there isn’t a waiting for the other guys most of the time.

          • RX-3200

            you really decide for yourself first whether you agree with the fact that the version numbers are no longer important or not at all, but we do not about this

            Opera “to be on the same level” – they need to first return the standard functionality, but we do not about this

            I used Nightly builds on FF quite a long time without any bugs, so we can not say that somewhere something more stable, but we do not about this

            and we’re not talking about “what they should have” – we are talking about closing Next or not

            and it looks that they are waiting for is not “other guys”, and they await themselves, because they do not have these “other guys” – because in Presto they had only one development branch, and no one had heard about what they have increased staff of programmers so to overpower simultaneously two / three branches

          • Pedro Costa

            Has everyone knows all the big players except Microsoft copycat the google chrome release cycle.

            So to finish this conversation, read this from the guys themselves:


            They have Dev, same as Opera and Beta, which for Opera is Next. After that it has stable, same as Opera. FF has Nightly builds (dev), beta (Next) and stable…how is this different?

            If you still don’t understand I cannot tell you better than this. You can argue that dev stream doesn’t send has much builds has nightly builds from FF, but Open Source works a little different than closed source. So I don’t find that strange one bit and it doesn’t mean they are slower.

            It is alright for us to say that we were wrong. It is very good to accept knowledge from others and that is called learning.

          • RX-3200

            do how all – your position
            the only problem is that the “big players” have not started to do all over again half a year ago and their example here and now is not suitable

          • Pedro Costa

            Oh I see you’re trolling us…good one…lol

            You caught me there 😉

            I’m gonna stop feeding this one

          • RX-3200

            No – it seemed to you

            I seriously propose to close Next at all in 2014
            and make all it releases in Developer

  • Vit

    Unfortunately, I still use Opera 12 since lack of comparable functionality in next 60 releases. I hope that in New Year 2014 next release of the Opera will came with functions wanted by so many people

  • Patata Johnson

    “We except to keep up the development speed and quality level in 2014.”

    Too bad to hear that, really hoped that 2014 will be the year for Opera to make things better. But on the other hand its a clever move to keep the exceptions that low 😉

  • Dark Magician

    Yes, yes. Happy New Year…
    Fix the random YT selection problem, you can’t click on links, until x number of reloads and time.

  • Why are you closing My Opera blogs? Why?

    Tumblr was created after My Opera and Yahoo! purchased it for $1B.

    My Opera is in a state that can become profitable if you move it in the right direction. Why are you closing it?

    Millions of users got to know the Opera browser via the My Opera community and blogs.

    DON’T DO IT!

    • There are some useful blogs, but the vast majority are just spam and soft porn. It is just too much work to maintain it, but it is sad to see it go.

      Even Tamil seems to have moved on now — I don’t see him posting very often.


  • Stanislav Stratil

    Hmm, what will happen to Stash function if there will be bookmarks? I think its too much to have there speed dial, folders in speed dial, stash and bookmarks where you can have folders too.
    This just doesnt make sense to me, this is the same as google chrome and their “Apps” which are just bookmarks and their starting page, which is fail on the sight.

    • Leonardo Gomes

      I think that each one of them has a different function.

  • Volodymyr Buell

    Daniel, please give us a holiday gift – tell us at last something about plans for supporting Linux.

    • 0.o

      You want the usual answer? Same as asking Valve do they like number 3. Well, not really i like Opera but ”Things take time”

    • Why do you guys keep on asking about Linux version?

      They said already two months ago, don’t expect it for at least three months, so now at least another month.


      There is no need to ask again before at least the middle of February.

      • Volodymyr Buell

        Thanks for pointing that out.

  • Klaus Meyer

    I like the new opera 20. I switched back to Opera from Chrome after leaving after opera 12 was discontinued.

    Some really personal opinion: Sorry, but you shouldn’t have done any “release” of just the chromium-clone. Now that opera get’s its personality back it’s getting more and more fun to use with every release (starting from opera 19).

    Though a few things are missing like wand and text-formatting while zooming (you got that back in opera for android, btw 🙂 ), which I hope come back in later releases, I have a major problem with any Opera 20 release so far:

    I cannot print anything! The Printer-Dialogue opens, I can press Print, but nothing arrives at the spooler, no error message either.

    Can anyone confirm this. It’s annoying to save the page and open it in Chrome, just to print it 🙁

    Otherwise, you’re on the right way, a really good browser again!!!

    Oh, and one big request: I’d like to have something back the good old MDI, at least have all open tabs (from different windows) in one major tab-bar. I don’t like the mix between tabs and windows. I want a central point to access all open web-pages. If accessing a certain page means to switch a window, I want the browser to do this, not me. I just want to access the page, not looking through layers of windows!
    That annoys me in Chrome and Internet-Explorer and Firefox …. that why I used Opera 12 for a long, long time!
    So maybe for Opera 30+ you may consider my wish 🙂

    • nanana2

      Opera 30+??? You are so optimist…

  • Dark Magician

    Memory leaks should be fixed. I switched to clean install Win 8.1 x64 with 8GB,
    Usage is about 3 to 4GB, but Opera Next 19, somehow manages to fill it to 8GB, without doing anything, than it drops to normal levels.
    This is the sam stuff i had on Win 7 x64 with 4GB, so it is definetly a pattern.

  • kupoo

    Sadly this seems to be last year I will be using Opera. Been user since, I don’t even remember, 2001?

    But you can feel that slowly sites start to glitch in 12.16, and by the end of the year I’m quite sure I’ll be forced to make transition to another browser.

    2013 has been huge disappointment for me as far as browsers go.

    Good luck, and I hope you can catch up with what features you lost in 2014, I will be checking periodically, but I have my doubts it’s your wish.

    I still will be using Opera on mobile, as it’s where such simple and dumbed down browsers have place, not on desktop.

    • Operalino

      I’m looking for an alternative which can replace Opera 12 as well. But it has so many features no other browser offers.

      Private & normal Tabs in one window.
      Arrange tabs in window.
      Useful statusbar.

      I tested Firefox, Chrome/Iron, Maxthon, Avant, IE. Nothing comes even close to Opera 12.

      Right now Maxthon looks as the best alternative. But moving and organizing tabs is very basic (no mixed privat/normal window, no pinned tabs, no arranging of tabs inside a window, no creating of new windows by dragging a tab…)

      I still have some hope that Opera 15+ will get somewhat near what Opera 12 was…

      What is your alternative for Opera 12?

      • “What is your alternative for Opera 12?”

        Opera 11.64 😀 + Open In menu.

      • kupoo

        I really don’t know… nothing indeed comes close to Opera (12).

        What I miss the most is hold lmb and press rmb and vice versa for forward/backwards in Opera, mid click new tab, refresh page with gestures and other small but useful stuff.

        I’ll try to see where I can emulate this forward/backwards mouse behavior and go from there.

        Definitely not Chrome, I use it along Firefox for some stuff, and it’s just terrible. Maybe Firefox, but will have to see when the time comes.

        I was SO excited when I heard that Opera is switching to new engine, as Google tend to fuck up with Opera often in their services, but who knew that this change would just copy/paste Chrome with Opera name on it 🙁

        • MozPri

          “What I miss the most is hold lmb and press rmb and vice versa for forward/backwards in Opera”

          This is already possible in Blink based Opera.

  • MozPri

    Is it still New Year in Norway? New builds please. 😛

    • Leonardo Gomes

      They are returning to work today, so i think we will have something new only in a couple of days.

  • Congrats for your achievements. Surely, without sacrificing Linux support this couldn’t happened. I’m feeling like a proud but wounded soldier who left behind, for greater good of the team. peh!

  • Mark

    Opera Crash 2-3 times per day… do something!

    • Leonardo Gomes

      Which version/build? No crashes with lastest Developers build here.

      • Mark

        “Stable” 18.0.1284.68 – most crashes on “Frames” websites (Webmin hosting panel) or websites with HTTP authentication (phpMyAdmin on many hostings) .

  • BK

    I see there is a lot of good mood here. 2013 was a good year for Opera. For the first time since a while Opera is getting stronger.

    We know there are a lot of opportunities to further improve our browser, and I would like to say huge thanks for all of you who remind us about it on the daily basis. We know that which each thing that keeps you annoyed in the browser, there is an option to provide even better product.
    We are happy to hear whatever feedback you have, including your satisfaction, optimism, and bugs. In 2014 we will work even stronger in order to make Opera better and more unique. Hopefully, whatever you will try to achieve with Desktop browser, Opera will be there for you. Best wishes to all of you 🙂

    • ayespy

      There’s a new project out there called “Otter Browser” the ambition of which is to rebuild an Opera 12 clone on a QT core. I have looked at its “to do” list and see that some of my “necessaries” are there, and some are not.

      My suggestion is this: Keep an eye on the project, and don’t let Opera versions go by without implementing whatever Otter has implemented. The first items, for instance, would be Otter’s ability to open private tabs, and to allow a user to totally customize default search engines.

      Your core Opera user base has always been all about choice and customizability. I think you abandon that at your peril.

      For instance, if Otter ever gets around to fully implementing a decent mail client, as they plan, and if such implementation includes being able to see both the mail client and the web at the same time in the same window, they will as of that moment become more useful to me than Opera is now.

      I know that M2 is dead, but an installable mail module need not be. I have been doing some research, and there are QT-based free and open-source email clients out there that could be grafted onto Opera the moment your interface supported vertical elements side-by-side.

      Email and vertical bookmark and tab placement are my most urgently-sought needs for work and browsing efficiency. I can’t believe I’m the only person on the planet who would welcome such developments, and yet the closest anyone comes to offering it at present is Firefox with SimpleMail – and SimpleMail is a) not fully visible beside web content (though it has its own tab, which is a huge step) and b) still just a bit TOO simple, not offering all of the features of a true mail client.

      I know I’m just one guy, but I am determined to keep trying to find an experience that could match the speed and efficiency that I found in O12 – and I keep hoping against hope that the “new” Opera will see fit to produce it.

      • BK

        Hm.. what’s wrong with O18 speed for you? 🙂

        Where O12 was better in efficient support of your daily work?

        • Customisability is the main factor for speed. In benchmark tests, Opera 18 is about 25% faster than my default browser, Opera 11.64, but since the average page only takes a few seconds to load that’s not going to make any noticeable difference.

          A simple thing like Ctrl Shift T to reload a closed tab is going to take a second longer than Ctrl Z — a) because I have to stop and think, and b) because I have to use two hands.

          100 little things like that add up to Opera 18 being many times slower to use than Opera 11.64 or Opera 12.16.

          Fix the shortcut and gesture customisation first, then toolbar and menu customisation, then opera:button code so that we can create our own commands.

          Just for example, I type TD, and notepad opens with a text file where I store useful information, like PeaceKeeper Bechmark results. How long would it take to switch to Explorer, find the file, and open it?

          Opera 18.0.1284.68 scored 4055 and 6/7
          Opera 12.16 build 1860 scored 3303 and 4/7
          Opera 11.64 build 1403 scored 3194 and 5/7

          • Yes this is exactly what I mean as well. Of course speed + site compatibility are very important but usibility of browser is also important for users.

            The main reason to use Opera behind is exactly it is…

        • Nekomajin42

          I know, the question is not for me, but I’d like to answer too.
          When we speak about speed, it means several aspects. It’s not only page rendering time, but the response time of the GUI as well, the time needed to perform any action*, and the personal confort of the user.
          For example, opening a page from history with the trash button: one click + vertical mouse movement + another click. The same action with the O-menu: one click + horizontal mouse movement (which is a thin area, a little vertical slip, and all gone) + submenu opening delay + another click. Not much of a difference, but if you have to do this several times a day, it adds up.

          Personally, I like the feel of the new Opera. I can’t describe what this feel is, it’s just looks good and looks handy. But it’s not confortable for me. And it’s not about the pain of loosing the old habits. I’m willing to change my habits (or at least a part of them), if I have options to change to, equivalent options. But now, I don’t have much in the new Opera.

          I said before, that I really understood your point about the sipmle GUI, not to confuse the average users. But is it hard to implement features behind flags? I don’t think anyone in this blog would have any problem with an opt-in sidebar, or an open button in the save dialog, or a trash button, just to name a few. Implement it, hide it with a konami spell, and everyone will be happy. It is this simple.
          And please, speed up the developement a little.

          • BK

            Thanks a lot for this comment. I agree interactions can be better on the currently developed features. We will put much more focus on that.

        • ayespy

          Thank you for this question.

          For me, the efficiency of O12 lay in the ability to arrange the interface to maximize use of the desktop space, and minimize switching between windows and applications.

          It was possible to set it so that I could see and access all tabs and bookmarks on my right while having email open on my left, or see and access email account list (or bookmarks, or notes, or contacts – but most importantly email) on my left while having the web open on my right.

          Visual vertical tabs made it so that I could select the tab I wanted more quickly, without having to read characters.

          Access to vertical space on a web page was maximized, (nothing but address bar up top and pop-up progress bar at bottom) and horizontal space was not wasted with huge blank areas. (Panels including mail at left, tabs and bookmarks bar at right, open email or web page in the middle)

          This setup made it possible for me to only have to switch between views within Opera, or between Opera an an open document on my desktop in order to work, and all elements of my web use were visible and accessible to me at all times.

          There were other little things as well, like being able to open the view bar and leave it open with a find-in-page term entered into it, searching that term in one webpage after another if I wanted, without having to re-enter it, or re-open (ctrl+f) the find-in-page dialog for every damn new web page I opened.

          So – long story short, speed and efficiency mainly came from having everything I needed to be able to work, laid out in front of me left-to-right, in a single display utilizing visual cues with no wasted space.

  • Paweł Malinowski

    Hello. Happy Year to all. Opera 15+ is great project but i have two issueas, that stop my normal work. Tabs wrapping and asking what to do with downloaded files. Cmon – Tabs Overflow? In XXI century? Old Opera had this. And what about asking what to do with downloaded file – i cant just open it? IE 7 had such an option :-(.

  • Another belated Happy New Year, as there is a specific reason for it, at least for Opera users using streaming websites: the extension Last.fm Scrobbler for web has been updated yesterday to v1.30 including a new XBox Music connector. So now you can scrobble all tracks listened with the free XBox Music web player to your Last.fm profile: https://addons.opera.com/extensions/details/lastfm-scrobbler-2/ This is not even possible with the XBox hardware device, by the way. 😉

  • L33t4opera

    By the way, first new build this year – Opera Next 19.0.1326.26, enjoy 😉

    • nanana1

      Nice! Finally, after 3 weeks of waiting and rest, the works begin. 😉

  • Jones

    As a user since opera 9, I now give you one more week for you to fix the stupid sync with mobile. That’s ONE THING I require back from my previously beloved browser. ONE THING, if I don’t see it fixed next week, I’ll promise my self that I never ever will use opera browser, no matter what kind of features you will implent in future. Same goes for all the people I have recomended opera too!


  • Raylan Givens

    What’s going on with Cache? Doesn’t work at all ( Next channel )? In my Motherboard’s support page there’s a new BIOS but only with Firefox and IE11 can see it. Even when I press ctrl+F5 in Opera Next it could appear the new BIOS.

  • L33t4opera

    The first new build of Opera Developer 20.0.1376.0 in this year, the change log.

  • D M

    Bring us Opera on Linux and FreeBSD again this year, please!

  • zeum

    60 releases and all garbage!

    id rather have 1 quality release over 60 crap releases!

    60 releases and not 1 to try to fix the issues with your #1 product Opera 13. 60 releases and still NO panels, magic wand, manageable bookmarks, screenshots on speed dial etc etc. RIP Opera!