Slashdot Mirror
Opera 10.50 Beta Out, With Competitive JavaScript
Opera has released its 10.5 beta (for Windows only; Linux and Mac coming). Opera calls 10.5 "the fastest browser on earth," but the jury is out on this claim. WebMonkey says that the new beta feels snappy in their informal testing. Both CNET and ZDNet ran two quick benchmarks that measure JavaScript performance, SunSpider and V8. ZDNet found Opera beating out Chrome in SunSpider but lagging in V8. CNET found Chrome ahead in both tests. What is clear however is that Opera's Carakan JavaScript engine has made up much of the ground in the performance wars; The Reg estimates that 10.5 is seven times faster in the JavaScript stakes than Opera's shipping 10.1 release.
I'm actually far more excited for VEGA (their new vector graphics lib) than the javascript update. Is having spiffy-fast js nice? Yea, but I think Vega is really where they're going to shine. It'll make transformations and other animations run far smoother in opera than any other browser (with the exception of firefox's direct2d experimental build that was released a while back). Kudos Opera, you're ahead of the game yet again.
Note: I do recognize and appreciate the need to make javascript perform better.
Thing is...it seems that for many tech "journalists" hardly anything besides js matters anymore!
Notice how Opera said "the fastets on earth"; which might be still debatable of course, but they did not say "...fastest in javascript". Opera knows that's not the whole story in browser performance. You can see it especially when using Opera on some ancient machine where the difference is most startling. WebMonkey seems to know it too (nah, not reading TFA...)
CNET, ZDNet and The Reg seem to care only about JS...
What is it? Some new widespread fascination with numbers like in 3DMark heyday? "Journalists" taking the easy route by simply running automatic benchmarks? (written "for" Opera competitors BTW...)
One that hath name thou can not otter
They quite clearly explained that this was because the Linux and Mac versions were undergoing much bigger changes than the Windows version. And they will be faster and better integrated as a result. How is that a "fail"?
Clever signature text goes here.
Flush out your headgear, new guy. The days of HTML- and CSS- only websites are over. Even though those sites still exist, there's an entirely new category of "websites" online: web applications. The application I've been working on for the last 3 years or so is composed of about 60% Javascript, 30% PHP, 8% CSS, 1% HTML, 1% "other". With the recent push in Javascript engines, I've actually been able to watch the performance of the application improve by a substantial amount through no effort of my own, just because the application uses Javascript for the entire interface and browsers have focused on that aspect.
Nearly all of Google's services other than search are powered by Javascript, from Maps to Mail. Javascript (or any widely-supported client-side scripting language) is here to stay, and frankly it's the future of anything that's going to be online other than your basic informational sites. Even sites which are taking advantage of all of the new features in HTML5 will continue to take advantage of Javascript as well. The difference between IE6/7 and any very recent (< 3 months) browser is staggering.
I'm glad to see Opera catching up again, they're my browser of choice. They were among the fastest of the "first generation" JS engines, but nearly everyone else other than Microsoft pretty much beat Opera to the punch in the next generation of Javascript. It's nice to see them catch up. I hope Microsoft is able to make better strides with IE9, if not before.
Even the fancy but legitimately useful UI toolkits (e.g. YUI, jQuery) are invasive because they are so often served from third party sites (Yahoo or Google) instead of directly from the app site.
You can't say that the libraries are invasive because they're included from third-party applications, the application developers are invasive. My chosen framework (ExtJS in this case) is served from the same domain as the rest of the application, all gzipped and everything.
"Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
On top of those major changes, they are pushing Windows at the moment because of the EU Vs. Microsoft thing, where in March Microsoft will have to add the "Choose Your Browser" dialog, and Opera wants 10.5 to be on that list, not 10.1.
roman_mir, It would have been clearer if you referred to it as base 64 *encoding*, rathern than encryption, since it has nothing to do with cryptography.
On an unrealted note, with regards to the V8 performance test, the reason Chrome's V8 engine works well with the V8 benchmark is because the tests themselves are bias towards the specific optimisations that the Chrome developers have chosen to include in their V8 engine.
Carakan, on the the other hand, has, for various reasons, been developed to optimise for different cases. There are trade-offs here which, as a result, affect the performance of Carakan in some of the tests included in the V8 performance test.
Disclaimer: I work for Opera the on Carakan team. I cannot go into specifics about what optimisations and trade-offs have been made.
By reading this signature, you hereby agree with the content of the above comment.