v21 vs v20? Stable yet?
-
wcolwell last edited by
Anyone still comparing 21.0.1432.67 with 20.0.1387.91? Were there regressions with Aura (v21)? Are they fixed now?
-
colderwinters last edited by
Both version 20 and version 21 are stable, version 21 has some minor improvements, I myself am not comparing the two versions.
-
lem729 last edited by
I think with every new version there are always some issues. But it was released because the Opera developers concluded it was safe enough/stable. You know, you can try it, and if there's a problem, always go back to 20. In all likelihood, there won't be. This is much safer than playing with Opera Next
It's certainly performing as well for me as 20. -
solidsnake last edited by
I haven't noticed any stability issues in 21. However didn't noticed any speed improvements too. But I'm missing the smooth scroll feature in 21, and none of the smooth scroll extensions I've tried are decent replacement for Opera's smooth scroll.
-
funksoulbro last edited by
Nothing has been added or improved since version 15. All that's happened is the version number has increased by +1 every few weeks.
-
samkook last edited by
The was the tiny font problem in 21, not sure if there's been an update since then to fix it so I know I'm staying with 20 for a while until I hear that got fixed.
-
lem729 last edited by admin
Now at the time of the release, the Desktop Team released the following. http://blogs.opera.com/desktop/2014/05/opera-21-desktop-released-aura-powered/#comment-1371642705
They listed under Key Fixes and Improvements: "Opera will now scale with screens that use 200% DPI setting in Windows. No more tiny fonts!"
However, there's always a way to tweak more, especially for those who are are seeing challenged. For my version 21, I learned how to adjust the menu fonts using the windows Personalization feature in Windows 7, and they look great. Here's something in general on Windows adjustments. https://forums.opera.com/topic/2551/installed-latest-update-all-menus-shrunk/8
Some people, I remember now, had a problem with losing the thumbnails on their Speed Dials, but were generally able to fix things, I recall. This is a known issue that was commented on in the discussion for that link the Desktop Team initially released.
There's no difference in speed, as far as I can tell. Both 20 and 21 are quite fast. I had a bit of extension bloat, so when I cut back a lot on my activated extensions, I could really see the browser blazing. In the release notes for Opera 21, the major changes seem to be: (a) One-click install functionality for extensions (b) Stability enhancements, [Question of the thread: Stable yet? Well, there are stability enhancements in version 21] and (c) Enhanced support for Chromium extensions.
http://www.opera.com/docs/changelogs/unified/2100/
Here's a link to the Changelogs to see all that has been happenings since Opera 15. Quite a bit.
http://www.opera.com/docs/changelogs/ -
samkook last edited by
Maybe no more tiny font for 200% DPI, but tiny font's for everybody else, I just checked again and it's still the same.
Here's a picture comparing both menu(v20 on the left and v21 on the right):
BTW, I didn't change the zoom option(which only applies to the webpage content, not the menus), updating to v21 did that on its own.
Personally, I'm not going to screw up the size of everything else in windows just to bring back opera's menu at a decent size.
-
lem729 last edited by
I can understand your view. On the other hand, I tweaked the menus in Windows 7 from a font of 9 to one of 10, and it brought the menus back to quite good -- looks closer to your Opera 20 (not quite as bold though) And I don't see any problem for myself with the rest of Windows. Also, if you tweak the Windows menus, it's simple to go back to what you had before, if you don't like the result. Now I can't remember what Operating system you use. If it's Windows 7, this is easy to test -- the effect on Opera, the effect on the rest of Windows.
-
samkook last edited by
I know exactly how to change it and I do use Win7, but the problem is that I used the zoom to 150% function of windows to make things easy for me instead of playing with every single object size in windows so only playing with making the menu bigger would make the rest of windows much too big.
I did a test and v21 simply ignores that zoom option for the font(and only the font) and display it at 100% inside a menu zoomed at 150%.
So if you keep windows zoom at 100%, it should be fine to use.Also, in my opinion, it's simply not worth my time to try and find a solution for every problems that pops up with every release like I kept doing with presto. I only have it installed to keep track of the changes they make since I'm an eternal optimist, but I don't see myself using it for real any time soon at the rate it's going since there's no really unique features I'm interested in.
-
berng last edited by
Nothing has been added or improved since version 15. All that's happened is the version number has increased by +1 every few weeks.
Really? Either you're trying to create controversy by lying or you are too stupid to have seen the many very obvious changes since 15.
So are you trolling or just plain stupid?
-
Deleted User last edited by
Nothing has been added or improved since version 15. All that's happened is the version number has increased by +1 every few weeks.
Really? Either you're trying to create controversy by lying or you are too stupid to have seen the many very obvious changes since 15.
So are you trolling or just plain stupid?Don't care about him, it does not worth.
-
Deleted User last edited by
Nothing has been added or improved since version 15. All that's happened is the version number has increased by +1 every few weeks.
Really? Either you're trying to create controversy by lying or you are too stupid to have seen the many very obvious changes since 15.
So are you trolling or just plain stupid?He's not stupid but he is well-known for trolling the Opera forums. Sidney has the best answer: ignoring him.
-
wcolwell last edited by
I was using Opera Next (v21) in parallel with Opera Stable (v20) for a while and was excited by what I thought was snappier response with screen loads at least (though less "smooth" if that makes sense); it was as I expected if v21 were taking more advantage of hardware acceleration (which Aura was supposed to do). So I let Stable update to v21, but afterwards (initial release) I was seeing a few hiccups (don't recall what they were), so I reloaded v20 and have stayed there for now.
But I do expect v21+ to be faster. I thought I was seeing that in Opera Next. So I'm looking forward to that.
-
lem729 last edited by
On hiccups, I don't know whether you are using any extensions, but they can cause hiccups. I had about 27, and tested Opera 21 by shutting them all down. I got a substantial increase in speed. Now I've been carefully monitoring what I add to the browser (and this is difficult for me)
And I have 12 extensions activated ("my essentials," and chose some specifically because they seem simpler, would affect the browser performance the least) (it's hard to pare my list down) and maybe 13 or so, deactivated. And I'm still getting a quite sparkling performance in speed. Adding all the features via extensions in the world means nothing if you end up with a lumbering, unwieldly browser. And that's one of the concerns I have about everyone pushing for Opera to add more features to its browser. When they add features, then we have may have no option to deactivate them to enhance performance. Hopefully, Opera will be very careful about what they add, so as to keep the browser at the cutting edge of fast. -
samkook last edited by
BTW, adding more native features would only make the initial loading of the browser(and all its features) slower, not the navigation, that's just poor coding if it does.
It's another thing when you talk about extensions though since the browser is not aware of what they do and it's the same about every extensions with all the others so it can easily slow things down by doing the same thing multiple times or interfering with each other by doing something that's counter-productive for another.
Having the ability to enable/disable features is what many(myself included) have been asking for years, even before the new version came out, but for some unknown reason, that's not the way they seem to be going, quite the opposite sadly.
-
lem729 last edited by
BTW, adding more native features would only make the initial loading of the browser(and all its features) slower, not the navigation, that's just poor coding if it does.
Well, that's a key. I'm not a developer to know the truth there, but if what you say is the case, then Opera has more flexibility, which would be good. I'd be delighted, though I can't help being a bit dubious. Now Opera 21, with it's minimal features is quite fast, and surely faster than Opera Presto. My gut tells me one of the reasons for the speed is the simpler code, because of less native features, though the browser engine may well have something to do with it too. It's seems to me at some point -- when you're adding everyone's wish list of features and options -- that the bargain is with the devil, and we then learn how nothing is free in life -- that the browser performance would be affected. But that's just my opinion/gut feeling. Also if it's the case that features don't slow the browser down, why were you arguing for years that users should have, "the ability to enable/disable features." If features don't slow the browser down, it may not be worth the energy/expense for the developer of a free product to work to do that, just for a quicker start-up time, for those who disable features.
-
samkook last edited by
Personally, I care very little about speed, what I care about is disabling features that annoy me or are downright detrimental to the way I work.
It's of course not true 100% of the time, if a feature modifies directly the way a page is displayed, then it will slow things down(not as much as an extension would since they can optimize it if it's done internally, but they have to use a generic way of doing things for extensions) since it has to check a few things and make a decision, but all of the other stuff around in the interface like mail, rss, anything related to bookmarks, tab management, other stuff like that will not affect it in the slightest.
The engine is what is actually rendering the webpage so it's what responsible for the speed at which it can translate the information it receives from the website to something that get displayed on your monitor inside the defined area for it. Everything around it doesn't matter when it's doing that since it does interact directly with it, it just use a little more RAM.
I wouldn't say I'm an experienced programmer, but it is what I studied in so I have an idea of how things work internally.
-
lem729 last edited by
Someone who cares very little about browser speed is assuring me that adding features (which he wants) won't slow the browser down. Hmmmmm. I'd have to think twice about that one. -)
-
samkook last edited by
I have to say that it indeed doesn't inspire much confidence when you say it like that, but I'm not saying that as a user(quite frankly, I never even noticed a speed difference between browsers), I'm saying that as a programmer since I'm familiar with how things generally work inside.
