Posts Tagged: opera

The Best Browser? Internet Explorer 11, Chrome 31, Firefox 25, Opera 17, or Safari 5?

Filed Under: Tech Insight by midas — 4 Comments
November 13, 2013
Browser Logos

We put the latest web browsers head-to-head to try to find out which one is best!

In developing a powerful and feature-rich browser based room booking and resource scheduling system that’s supported in all five major browsers, we often get asked “So, which is the best web browser?”.

This time last year we put Chrome 23, Firefox 16, Internet Explorer 9 & 10, Opera 12 and Safari 5 head-to-head

Now, twelve months on, and less than a week since Internet Explorer 11 became available for Windows 7, Firefox celebrated its ninth birthday, and just a day after Google Chrome 31 is released, we decided it was high time to once again put the latest web browsers offerings “head-to-head” and independently, rigorously test and benchmark them to find out which one of the five major browsers is currently “the best”….

Browsers Tested

Google Chrome 31Mozilla Firefox 25Microsoft Internet Explorer 11Opera 17Apple Safari 5
Google Chrome 31Mozilla Firefox 25Internet Explorer 11Opera 17Apple Safari 5

The Tests

We broadly tested four key areas of browser performance: Speed, Memory Usage, Compliance with standards, and Javascript Performance.

1. Speed

Cold Start Browser Times

The “Cold Start” test measures the time taken to load up the browser upon its first run after a computer reboot. This is measured from the point at which the browser is executed until the point at which its user interface (UI) is ready to accept input.

Non-Cold Start Browser Times

The “Non-Cold Start” test measures the time taken to load up the browser on second and subsequent runs after its first run after a reboot. This is measured from the point at which the browser is executed until the point at which the user interface (UI) is ready to accept input.

Page Load Times (Non-Cached Load)

With the browser open, an empty cache, and showing a blank page (about:blank), the “Page Load Time (No-Cached Load)” test measures the time taken to completely load a complex web page. This is measured from the point at which the “Enter” key is pressed on the URL in the browser’s address bar until the point at which the test web page has fully loaded (as reported by an “onLoad” event on the test web page).

Page Load Times (Cached)

With the browser open, and the test web page already loaded in a single tab, the “Page Load Time (Reload from Cache)” test measures the time taken to reload a complex web page. This is measured from the point at which the F5 key (refresh) is pressed until the point at which the test web page has fully reloaded (as reported by an “onLoad” event on the test web page).

2. Memory Usage

Base Memory Usage (Blank Tab)

The “Base Memory Usage (Blank Tab)” test measures the amount of memory used by the browser with just a single blank (about:blank) tab open.

Memory Usage (10 open tabs)

The “Memory Usage (10 open tabs)” test measures the amount of memory used by the browser with 10 tabs open, each displaying the home page of a popular website.

3. Compliance

HTML5 Compliance

The “HTML5 Compliance” test measures how well each browser conforms to the current state of the HTML5 specification.

CSS3 Compliance

The “CSS3 Compliance” test measures how well each browser conforms to the current state of the CSS3 specification.

4. Javascript Performance

There are a number of different Javascript Performance Benchmark tests available today, all of which give quite different results. We’ve analyzed results from 6 of the most popular Benchmarking Tests and aggregated the results below:

Javascript Performance (Aggregate)

Individual details of each of the 6 individual Javascript benchmark test suits used to arrived at these aggregated scores may be found in our full test report, available to view/download at the end of this page.

Summary

CategoryTestWinnerRunner-Up
SpeedCold StartFF25IE11
Non-Cold StartIE11SF5.1
Page Load Time (Non-Cached Load)OP17IE11
Page Load Time (Reload from Cache)GC31OP17
Memory UsageBase MemoryIE11SF5.1
10 Open TabsFF25SF5.1
ComplianceHTML5GC31OP17
CSS3OP17GC31
PerformanceJavascript Performance (Aggregate)GC31OP17

Results

1st Place2nd Place3rd Place4th Place5th Place
Google Chrome 31Opera 17Microsoft Internet Explorer 11Mozilla Firefox 25Apple Safari 5
Google Chrome 31Opera 17Internet Explorer 11Mozilla Firefox 25Apple Safari 5

The above overall positions were derived based upon the sum of the positions that each browser finished in, in each of our tests. For example, in our HTML 5 compliance test, Chrome came first and so was assigned 1 point, Safari came 5th and so was assigned 5 points. Browsers were then ranked according to the lowest number of points to give the 1st-5th places above (1st being the best)

Analysis

Google Chrome 31 Google Chrome
When we last tested the five major browsers back in November 2012, Chrome came first in 8 out of 13 our tests, making it a clear winner!
A year later, and Chrome is still going strong, coming top in 8 out of 15 tests, and second in a further two tests.
Where Chrome still doesn’t perform quite as well is when it comes to its memory usage, using well over 3 times as much memory with a single blank tab open than Internet Explorer 11.

Mozilla Firefox 25 Mozilla Firefox
We were a little surprised that Firefox only came top in 3 out of 15 tests, and only once came runner-up. To Firefox’s credit, its main strength still seems to be in its memory usage. With 10 websites open in separate tabs, the amount of memory used was less than half that of Chrome with the same ten sites open.

Microsoft Internet Explorer 11 Internet Explorer
We were pleasantly surprised by the improvement of Internet Explorer 11 over previous versions as well as other browsers.
IE11 came top in a couple of our tests, and runner-up in a further three.
Where IE11 appears to have improved most over earlier versions of Microsoft’s browser in is the length of time taken to load and pages (either from a server, or from the cache) as well as start/restart the browser itself. In our tests, starting IE11 took just 0.01463 seconds! – some 280x quicker than Opera started.
That said, in general Internet Explorer 11 still has a way to go to come up to par with the other major browsers in terms of HTML 5 compliance.

Opera 17 Opera
A lot has changed with Opera since we last tested browsers twelve months ago. Since then, Opera have switched from using their own “Presto” layout rendering engine to instead using the same engine as Chrome.
Whilst this change has been received with mixed reviews by Opera users, with some unhappy that many of Opera’s original features were dropped, our test results actually show that the “new” Opera is a browser to be reckoned with, out performing Internet Explorer 11, Firefox 25 and Safari 5 in our tests.
Opera 17 came top in 3 out of our 15 tests, and runner-up in 6.
The browser also scored highly on HTML5/CSS3 compliance and in our aggregated Javascript performance tests, however, Opera’s memory usage was fairly high, second only to Chrome. Opera 17 was slow to start, however, once running it loaded and rendered web pages swiftly.

Apple Safari 5.1 Safari
Our browsers tests were performed on a Windows machine (test specifics are included at the end of this report). Whilst the latest version of Safari is 7, Apple took the decision after the release of Safari 5.1 to no longer continue developing Safari for Windows users – a mistake in our view! Therefore, the most recent version of Safari available to Windows users is 5.1.7, which was used in our testing.
Given that Safari 5.1.7 is now the oldest of the 5 browsers tested, it follows that is doesn’t perform as well as its peers.
However, surprisingly, it did come runner-up in both our memory tests as well as our non-cold start test.

Conclusions – From a Developers Perspective

From our perspective, as developers of a leading web-based room booking and resource scheduling solution, perhaps the most important factors in determining which browser is “best” are compliance with the latest HTML5 and CSS3 standards. As we work hard to ensure our software works well in all the major browsers, this is where having universal standards between browsers becomes so important. In theory, a website (or in our case, a web app), should look and behave the same regardless of the browser being used, which should in theory happen if all browsers complied 100% with standards! Chrome 31 currently comes the closest to the HTML 5 standard with 93% compliance, but as can be seen, CSS3 compliance still has a long way to go for all browsers, with the winning browser in the CSS3 compliance test (Opera 17) only achieving 58% compliance.

Speed (page load time) and Javascript Performance are also important factors for us, as we want our web app to be as fast and responsive as possible. Opera 17 and Chrome 25 loaded pages faster in our tests, with Internet Explorer 11 following close behind. As for performance, both Chrome 25 and Opera 17 outperformed other browsers in our aggregated Javascript performance test scores.

A few surprising finds:

  • Microsoft have made some significant steps forward with Internet Explorer 11 over earlier incarnations of their browser.
  • Opera 17 performed better than expected
  • Firefox 25 performed worse than expected, finishing an overall 4th place in our tests.
Online Web Based Room SchedulingMIDAS, our popular Browser-Based Room & Resource Scheduling Software is currently supported in all browser versions we’ve tested here. Find out more at https://mid.as

Conclusions – So which browser should I use then!?

• If you work with lots of browser tabs open at once, and/or the amount of available memory on your system is limited, Firefox 25 would seem a good choice of browser to use, as this used the less memory than other browsers under the same conditions.

• If you regularly open and close your browser, Internet Explorer 11 or Firefox 25 would seem a good choice as these browsers start up quickly. If, however, you tend to keep your browser running most of the time, Opera 17 would be a better choice, as even though its start-up time is considerably longer, initial page load times are the quickest of all the browsers we tested

• If you’re still using an earlier version of Internet Explorer – it’s certainly worth upgrading to IE11, or if that’s not possible (for example, if you’re using Windows XP, you won’t be able to update your Internet Explorer past version 8!), maybe it’s time to try a different browser!?

• At the end of the day, use the browser that you feel most comfortable with! …BUT make sure you keep it up-to-date, and don’t ignore the competition – if you do, you risk being left behind as other browsers overtake yours in terms of their speed, security, memory usage, standard compliance, and performance!

• In recent years, browsers such as Internet Explorer and Opera have been somewhat overlooked by many regular internet users – but if you’ve not used these browsers for years having previously dismissed them – a lot has changed, and it’s certainly worth giving them a second look again now!

View/Download The Complete Web Browser Test Report HERE

Test Specifics

Browsers Tested: Chrome 31.0.1650.48 m | Firefox 25.0 | Internet Explorer 11.0.9600.16428 | Opera 17 (Build 1652) | Safari 5.1.7 (7534.57.2)

Browser tests were performed on an Intel® Atom™ CPU D525 @ 1.80GHz system, with 4GB Ram, running Windows Home Server 2011 SP1 (Windows Server 2008 R2) 64-bit. Each browser was a clean install, using default install and browsers settings, and with no extensions/addons installed or enabled.

Speed tests were measured using Rob Keir’s millisecond timer and PassMark AppTimer v1.0. Each speed test was performed 10 times for each browser, and the results averaged to provide the data presented in this report.

Compliance Tests: HTML5 | CSS3

Javascript Performance Tests: Dromaeo | Speed-Battle | Sunspider | Peacekeeper | Octane | BrowserMark

Memory usage was measured 60 seconds after tabs had finished loading and was measured through the Windows Task Manager. Memory usage includes all associated processes running with the browser (for example, running Safari spawns both “Safari.exe” and “WebKit2WebProcess.exe” processes, the memory usage of both is taken into account)

The 10 sites open in tabs when measuring memory usage (10 open tabs) were:
https//mid.as | http://news.bbc.co.uk | http://facebook.com | https://twitter.com | http://google.co.uk | https://youtube.com | http://wikipedia.org | http://linkedin.com | http://bing.com | http://amazon.co.uk

Test Date: 13 November 2013

Tags: , , , , , , , , ,

Web Browser Roundup – June 2013

Filed Under: News by midas — Leave a comment
June 28, 2013

It’s been a busy end to the month in the world of web browsers in June… So here’s our take on what’s been happening..

  • Internet Explorer – IE11 preview available & IE11 is to be available for Windows 7
  • Firefox – v22 released this week
  • Chrome – Now 5% faster on average
  • Opera – v15 preview available
  • Safari – Even the developers admit its gone quiet!

Internet Explorer:
Internet Explorer 11 Preview
This last week saw Microsoft release the first public preview of Windows 8.1, which contains the first glimpse of what IE11 will have in store for its users!

Microsoft believes that “the best experience of the web is on a Windows device with Internet Explorer 11“. We’ll let you decide!

However, one of the main focuses for IE11 is on better support, performance, and responsiveness for touch actions

Internet Explorer 11According to Microsoft’s corporate vice-president for Internet Explorer, Dean Hachamovitch, speaking at last week’s BUILD developer conference in San Francisco; “Most of the web wasn’t designed for touch, but users still expect it to just work“. An example given was that navigation and interaction within web pages or web apps often relies on “mouseovers”. This is where hovering the mouse over a particular region causes a menu or tooltip to open. The natural behavior for users with a touch screen is to tap the area. This is usually translated into a “click” event rather than a “hover” action, or if they tap and hold, seen as a “right click” event.

In IE11, Microsoft has integrated support for such scenarios, allowing users to touch a hover “hotspot” so that the menu/tooltip stays open rather than automatically clicking the element.

IE11 is also the first of the major browsers to offer HTML5 drag-and-drop support for touch interaction. These “hover” and “drag-and-drop” improvements for touch should offer users on tablets or other touch-screen devices a richer experience when using our web based scheduling software.

The great news too if you’re a Windows 7 user is that like IE10, IE11 will also be available to you! Whilst Microsoft have confirmed this however, there is no specific date for when IE11 may become available for Windows 7. If it’s anything like the delayed IE10 release for Windows 7, Windows 7 users may have to wait 4 months longer than Windows 8 users to get their hands on the next version of IE!

MIDAS is already supported in the preview version IE11, as well as in IE8-10. However, if you’re still an Internet Explorer 8 user, we will no longer be maintaining compatibility with this obsolete browser once IE11 becomes fully available. If this affects you please read this!

Mozilla Firefox:
Firefox 22
Also within the last week, Mozilla have released Firefox 22, bringing with it a number of improvements and new features. Some of these improvements, particularly those relating to core Javascript performance, should mean your MIDAS experience on Firefox is better than ever!

Firefox 22 also introduces support for new technologies and better compatibility with existing web standards. One of the exciting new technologies introduced with Firefox 22 is “Web Notifications”. This will allow websites/apps to display notification messages on your system (similar to new mail or new message notifications that other applications may display). Notifications are not widely supported by other browsers right now. At time of writing, only Opera 12 and Safari 5 currently support it. Once this becomes more widely adopted, you may see “web notifications” being introduced to MIDAS. For instance, it could be used to notify you of booking reminders as well as new watches or messages. Stay tuned for more in the future on this!

Firefox Logo Redesign 2013In other highly exciting(!) Firefox news, their logo has undergone a redesigned:

…and yes, you’d be forgiven for thinking that it looks virtually the same! In justifying the new logo, Mozilla explain, “Unlike previous versions, the updated logo was created specifically with mobile in mind. Although we think it looks great at any size, it’s been optimized to be crisper and cleaner on small screens and lower resolution devices. However, it also scales quite nicely for use in retina displays, and (unlike previous versions) can be accurately recreated in SVG so it’s more ‘of the Web’“

MIDAS is currently supported in Firefox 4+ (v22+ recommended)

Google Chrome:
Chrome 27
We’re having a hard time keeping up with the latest stable version number for Chrome! For Windows, Max, and Chrome OS it’s currently version 27. However the current stable version of Chrome for Linux is 28. This is unusual, as Google tend to keep major version numbers in sync across all platforms!

So, what exciting new features have v27/28 brought? Well, not a great deal actually! Aside from a variety of fixes mainly for Flash-related exploits, the highlight of v27 is the claim that web pages load 5% faster on average!

MIDAS is currently supported in Chrome 9+ (v27+ recommended)

Opera:
Opera 15
If you’ve been following our blog, you’ll know that at the start of the year, Opera announced it was ditching its own Presto rendering engine. Instead it was essentially joining forces to use the same rendering engine to that of Google Chrome. Such a major change in the fundamental nature of the Opera browser was going to take time to emerge. After much confusion and changes, at the end of May, Opera lifted the lid on their “next generation” Opera 15 browser to mixed reviews.

As this was the first “preview” release, it was essentially just a shell of a browser. Many of Opera’s previous features were removed, to the anger of Opera’s loyal user base.

However, as June has progressed, so have the updates to Opera 15. These updates haven’t exactly been earth-shattering though. Essentially just offering a handful of fixes each time and a way to import data/settings from Opera 12.

Whilst understandably there’s a massive amount of work involved in changing rendering engines, Opera really need to start getting their act together. They need to remember what set Opera apart from other browsers in the first place if they really expect Opera 15 to complete with other major browsers. Right now, whilst Opera 15 hasn’t yet had a general release, it’s lacking a lot of features and functionality that Opera 12 offered.

That said, MIDAS is supported in Opera 15 (as well as Opera 9-12. v12+ recommended)

Safari:
Safari 7/6.1
Well, activity on the Safari front just seems to get quieter and quieter each time we post! In fact, on the Safari blog itself they admit they’ve been “quieter than usual” which they attribute to Apple developers being away at a conference(!)

Anyway, A small update to Safari, 6.0.5, was released at the start of the month for OS X and iOS.

At Apple’s World Wide Developer Conference this month, it was announced that Safari 7/6.1 would bring improvements in JavaScript performance and memory usage. There would also be a new look for Top Sites and the Sidebar, and a new Shared Links feature. Additionally, a new Power Saver feature pauses plugins which aren’t in use. Safari 7 for OS X Mavericks and Safari 6.1 (for Lion and Mountain Lion) is expected to be available this Autumn. Sadly, there’s still no sign of any more updates for Safari on Windows (which is still currently stuck at v5.1.7)

MIDAS is currently supported in Safari 4+ (v5+ recommended)

Tags: , , , , , , ,

Web Browser Roundup – April 2013

Filed Under: News by midas — Leave a comment
April 12, 2013

It’s been a busy few weeks in the world of web browsers! There’s been some major changes in the browser landscape too! So here’s our take on what’s been happening..

  • Internet Explorer – IE11 coming later this year? / IE10 available for Windows 7 / Farewell IE8
  • Firefox – v20 now available… and a new rendering engine on the horizon?
  • Chrome – v26 out now… and ANOTHER new rendering engine on the horizon?!
  • Opera – 12.15 now available… and a change in rendering engine to.. WebKit? no wait.. Blink?
  • Safari – What will all these rendering engine changes to other browsers mean for Safari?

Internet Explorer

Internet Explorer 11 coming soon
Microsoft are busy working on their next update for Windows 8, currently billed as being “Windows 8.1”. It’s expected to be available in the latter half of this year. Windows 8.1 will almost be a kind of “service pack” for Windows 8, but will also contain a number of improvements and updates to apps & software. Perhaps the most exciting updating coming with Windows 8.1 will be Internet Explorer 11.

Yes, that’s right, no sooner is IE10 out of the door, and Microsoft are following it up with IE11 in a relatively short space of time (well, for them anyway!). We think this is great to see from Microsoft! In the past, updates to their flagship browser have been few and far between. Compare that with Mozilla’s current release cycle for Firefox, churning out a new version of Firefox every 6 weeks!

MIDAS will be supported in IE11 when it becomes available. It remains presently unknown as to whether IE11 will be “exclusive” to Windows 8.1, or if like IE10, it will also be made available for Windows 7 users as well.

…and yes, you did read that right – Internet Explorer 10 is available for Windows 7 right now! (and has been for over a month). If you’re a Windows 7 and Internet Explorer user, we strongly recommend that you update to IE10 get the best out of MIDAS.

Finally, if you’re still an Internet Explorer 8 user please read our “Saying farewell to Internet Explorer 8” post. Essentially, please upgrade your browser… as we won’t be supporting MIDAS in IE8 indefinitely!

MIDAS is currently supported in Internet Explorer 8+ (v10+ recommended)

Mozilla Firefox

Firefox 20
Mozilla’s rapid release cycle means that we’re now up to Firefox version 20! In a tweet yesterday, the Firefox team claim that with their latest version of Firefox “you can get the web up to 7 times faster than older versions”.

Mozilla also announced last week that they were collaborating with Samsung on a new rendering engine, named “Servo”. A “rendering engine” is essentially what converts raw web page code into what you actually see on your browser screen. Mozilla’s long standing rendering engine has been “Gecko”, but according to Mozilla;

“Servo is a research project to develop a new web browser engine. Our goal is to create an architecture that takes advantage of parallelism at many levels, both on the CPU and GPU, while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. With Servo, we aim to take the kinds of fluid, richer multimedia experiences expected in today’s smart phone and tablet applications to the next level on tomorrow’s web and tomorrow’s hardware.”

“Servo” is still in its early days and according to Mozilla;

“It’s too early to say how [Servo] will be adopted going forward. No decision has been made as to whether Servo will replace Gecko. Gecko remains the ‘productised’ web engine for Mozilla.“

So it may be that Servo ends up being a rendering engine for Mozilla’s smartphone/tablet browsers, and Gecko remains for desktop Firefox editions. This could get confusing, but it’s more likely over time that Mozilla will standardize their rendering engine across all platforms.

MIDAS is currently supported in Firefox 4+ (v20+ recommended)

Google Chrome

Chrome 26
The current version of Google’s Chrome browser is v26. Ever since its first release – which was only 4 years ago! – Chrome has always used the WebKit rendering engine, most notably used by Apple’s Safari web browser. Chrome’s subsequent input into the WebKit project has really driven WebKit development forward in the last four years. WebKit is now arguably the most standards-compliant of all the rendering engines currently used by the major browsers.

However, Google recently announced that they would be developing a new rendering engine for Chrome, called “Blink”. Blink is expected to make it into builds of Chrome within just 10 weeks! Unlike Mozilla’s “Servo” engine, which is being built from the ground up, Blink is heavily based on the WebKit project.

Google have released a Blink Q&A video if you’re interested in learning more about this new rendering engine and its implementation

MIDAS is currently supported in Chrome 9+ (v26+ recommended)

Opera

Opera 12.15
Opera are having a bit of a turbulent time of late, and in some respects appear to be loosing a sense of focus and direction!
The Opera browser was first released in late 1994. This makes it the longest running browser that’s still in active development and current use today.

Apart from its longevity, what also makes Opera unique is their own “Presto” rendering engine.

Now, you may remember that back in January, we reported that Opera were making a switch from Presto to WebKit. Well, at least for their mobile browser offerings.

Then in February, it was confirmed that Opera would drop Presto for their entire range on browsers (not just mobile).

This was a move that surprised a lot of analysts, and received a mixed response from Opera’s loyal user base.

Whilst it would have been sad to see a very mature rendering engine being put out to pasture, it would have meant that with Google and Opera both contributing to WebKit (along with Safari). This would provide more continuity between browsing experiences on the three browsers. Also with three major organizations contributing to the development of WebKit, it would have become very powerful. It would certainly have Mozilla and Internet Explorer (who don’t use WebKit) quaking in their boots!

…but this was before Google announced Blink… and shortly afterwards, Opera changed their minds. Opera decided to jump on the Blink band-wagon too, after having gone all out and confirming they were moving to WebKit!!

So it’s a little confusing at the moment as to the direction that Opera are going down! ..but as things stand, here are the list of rendering engines that the five major browsers are using/will be using in the near future:

BrowserCurrent Rending EngineFuture Rendering Engine
Trident Rendering Engine Internet ExplorerTridentTrident
Gecko Rendering Engine Mozilla FirefoxGeckoServo?
Blink Rendering Engine Google ChromeWebKitBlink
Presto Rendering Engine OperaPrestoBlink?
WebKit Rendering Engine Apple SafariWebKitWebKit

MIDAS is currently supported in Opera 9+ (v12+ recommended)

Safari

Safari - The Future of WebKit
As you’ll know from our previous Web Browser Roundups – it’s been pretty quiet on the Safari development front in recent months. There’s not much happening on the face of it!

Safari’s rendering engine is WebKit, and last month it looked like both Google and Opera would begin contributing code to the WebKit project. In fact, Opera even began contributing code to WebKit.

This was before Google announced it was moving away from WebKit in favor of a new rendering engine, Blink. Then Opera followed suit and announced it was also teaming up with Google for the new Blink rendering engine.

So what will this mean for WebKit and the Safari browser that will soon be the sole user and primary contributor to the WebKit project?

Well, it remains to be seen! WebKit was successfully developed without Google’s input in the days before Chrome. It may well survive without Google’s input in the future. But with Google and Opera pooling resources into Blink, and Firefox potentially introducing a new rendering engine too, the WebKit team (and Safari) are going to be facing a tough challenge to keep up!

MIDAS is currently supported in Safari 4+ (v5+ recommended)

Tags: , , , , , , , , , , , , , , , , , ,

Web Browser Roundup – February 2013

Filed Under: News by midas — Leave a comment
February 13, 2013

Here’s our take on all the latest web browser news for February…

  • Internet Explorer – Speculation continues over the IE10 release date for Windows 7
  • Chrome – The most actively developed browser?
  • Firefox – 18.0.2 now available.. development slowing down?
  • Safari – Are its days numbered?
  • Opera – 300 million active users and a full move to WebKit confirmed!

Internet Explorer:
Internet Explorer 10 - The Browser You Loved To Hate
At the very end of last month, Microsoft released an IE10 Update Blocker Toolkit. This led to speculation that IE10 for Windows 7 may be just around the corner!

There was some speculation that IE10 may have been pushed through Windows Update on 12th February to coincide with Microsoft’s monthly “Patch Tuesday”, when they were already planning on releasing some “critical updates” to Internet Explorer.

Whilst the critical updates for IE were included in this month’s Patch Tuesday, IE10 itself wasn’t. This isn’t entirely surprising, given that the update blocker (which prevents IE10 from being downloaded/installed via Windows Update) was only made available 13 days earlier. 13 days is hardly enough time for corporate environments (for which the blocker is aimed) to deploy the blocker throughout their IT infrastructure.

It’s instead more likely that IE10 will make a proper appearance for Windows 7 users at the end of the month, or in early March. This is based on when previous “IE blockers” were released. That’s assuming of course the IE team can be dragged away from devoting their time/energy/resources to developing endless web-based games, such as Contre Jour, to showcase how “great” Internet Explorer is. Instead, we think they really should focus instead on developing their actual web browser!

Anyway, you can read more about our predictions for when IE10 will likely be fully available in our blog post, “…and the final release date for Internet Explorer 10 on Windows 7 is…“

MIDAS is currently supported in Internet Explorer 8+ (v10+ recommended)

Google Chrome:
Chrome 24
Chrome continues to receive regular updates – in fact the Stable channel was updated only yesterday for Linux users to fix *another* Flash vulnerability!

These frequently discovered Flash vulnerabilities are not confined to Chrome. They can affect any browser on a computer with Flash installed. This is also why Microsoft pushed a couple of “critical updates” to Internet Explorer yesterday.

In our opinion, the sooner Flash is killed off the better! For today’s modern web browser, it serves no real purpose! Everything that Flash can do can these days be accomplished through a use of HTML5, CSS3, and Javascript.

You won’t find any Flash on our website, or within our scheduling web app

Anyway, back to Chrome; So far this month, there have been no fewer than 3 updates to the “Stable” channel. If you’re a normal Chrome user, you’ll automatically receive updates from the “Stable” channel. Two updates were made to the Chrome Beta for Android, two to the “Dev” channel, and one update to the “Beta” channel… and we’re only halfway through the month!

Google Chrome is arguably the most “actively” developed web browser at the present time.

MIDAS is currently supported in Chrome 9+ (v24+ recommended)

Mozilla Firefox:
Firefox 18
At the start of the month, Mozilla, released Firefox 18.0.2.

Primarily a security & stability update, 18.0.2 does have a handful of new features/improvements, most notably:

  • Faster JavaScript performance
  • Better image quality when scaling
  • Improved browser start-up time. (Chrome already has the fastest start-up times out of all the major browsers we tested a couple of months back to determine “Which Browser is Best?“)
  • Support for Retina Display on OS X 10.7 and up

In recent times, Mozilla have been releasing a “major” update to Firefox every six weeks or so. However, we wonder if this release cycle may now start to slow down whilst the Mozilla team focus more of their attention on their upcoming “Firefox OS” project.

MIDAS is currently supported in Firefox 4+ (v18+ recommended)

Safari:
Safari 5
Sadly, once again, there’s no new Safari news to report! As you’ll know from our November update, Safari development has taken back seat over at Apple in recent times. Apple instead have been seemingly more focused on their hardware offerings, than on their web browser. As we reported at the end of last year, they’ve currently ceased development on the Windows version of Safari.

And with other browsers, such as Chrome or Firefox available (and soon to become available) for iPad and iOS users, you do have to wonder whether Safari’s days are numbered? Will it be long before Apple take the decision to cease Safari development completely?!

MIDAS is currently supported in Safari 4+ (v5+ recommended)

Opera:
Opera 12.14
Last month we reported that Opera were dropping their own rendering engine, “Presto”, in favor of “WebKit” for a new mobile browser “Ice”. WebKit is the rendering engine already used by the likes of Safari and Chrome.

At the time, there was no word as to whether this move would mean that “Presto” was to also be ultimately phased out of their desktop browser offering as well.

Well, now this has been confirmed in an official Opera Press Release. The primary reason for the press release was to mark the fact that Opera now has an impressive 300 million monthly users across its various browser products. In the release CTO of Opera Software, Håkon Wium Lie, also writes:

“The WebKit engine is already very good, and we aim to take part in making it even better. It supports the standards we care about, and it has the performance we need. It makes more sense to have our experts working with the open source communities to further improve WebKit and Chromium, rather than developing our own rendering engine [Presto] further.”

No timescale has been given for this transition. It’s likely though to be a gradual progression over to WebKit rather than a sudden overnight switch.

In some respects it will be sad to see the “Presto” engine go. The more different browser rendering engines there are, the more competition there is to be the “best” and most up-to-date standards compliant browser. But in many other respects, this could actually be a very good move!

WebKit is actively in development by both Apple and Google, and is what powers their respective browsers. Add to this mix the extensive development expertise that the Opera team have. We do mean extensive too! Opera has been in constant development since 1994!). It will likely have Firefox (which uses its own “Gecko” engine), and Internet Explorer (which uses its own “Trident” engine) pretty worried!

Because Chrome, Safari, and soon Opera too, will use the same rendering engine, in theory web pages (and apps) should look identical in which ever of these browsers you use. This should make life easier for web developers! (In practice this isn’t quite true, as each browser has a different release cycle, so new features in the WebKit engine itself make it into one browser weeks, if not months, before another).

MIDAS is currently supported in Opera 9+ (v12+ recommended)

Tags: , , , , , , , , , , ,