If you find yourself logged out please rest assured that this is completely normal and expected. To participate in the discussions after that date you have to sign-in again using the "Login" button.
Apologies for any inconvenience caused.
Making Opera developer really a bleeding edge stream
Deleted User last edited by
When the rapid release cycle was first announced, Opera Developer was presented as a bleeding edge development stream and I was really excited about that. However, in the past months I had the impression that Opera Developer has failed in its purpose: Opera Developer and Opera Next have had really few differences except bug-fixes.
In Opera Developer features should be piloted, shelved, or taken forward to the Opera Next stream, but if you compare Opera developer 18-19-20 with their stable versions I don't see big changes feature wise (the only noteworthy feature I can think of is Synch, announced during the 19 developer stream and still in development).
So, in order to make the Developer Stream really "bleeding edge" Opera Developer should have many more options enabled by default in opera://flags. There are many great experimental features already available in Opera 21 such as tabs hibernation, Off Road 2 with video compression, the hung plugin monitor, ecc... but no one knows about them because they are turned off and no one speaks about them in the Desktop Team blog.
So here's the challenging question:
why there's a developer stream if all the new and interesting features are hidden?
leocg Moderator last edited by
Well, Developer Stream is not only for the ones that want to test new features but also for the ones that know how to enable those features.
I may agree that Opera should make flags more visible to the public but i'm not sure if they should be enabled by default. Not of them are ready for it and not all of them would please everyone.