Feeds

Firefox 3.5 - it's not a 'web upgrade'

But it's a nice browser

Providing a secure and efficient Helpdesk

Review "This isn't just an upgrade of the browser. It's also an upgrade for the web", says Mike Beltzner, Firefox product director, in his What's New in 3.5 video.

Hyperbole for sure, but it highlights the most interesting aspect of the browser wars, which is how each player is trying to influence the direction of web development.

From the user's perspective, Firefox 3.5 is better - but not dramatically so. The first notable new feature is private browsing, a catch-up with Microsoft's Internet Explorer and Google Chrome that lets you browse web sites without leaving traces in browser history or temporary files. Next comes Tear Off Tabs, which - as in Apple's Safari - allows tabs to be dragged into a separate browser window. A neat touch is Recently Closed Tabs and Recently Closed Windows, which gets you back where you were after accidentally closing a page.

Location-aware browsing is more exciting. A website can prompt for your location, and subject to your consent, Firefox will call a Google API to work out where you are. It implements a proposed W3C standard and has potential, though hardly any sites make use of it at the moment. The other snag is that Firefox currently relies on WiFi points and IP addresses and does not use GPS even if present. Which may explain why it was out by 125 miles when I tried it.

Geolocation in Firefox 3.5

Location-aware browsing: great, if accuracy's not your thing

The next perspective is performance. Firefox 3.5 has a new JavaScript engine called TraceMonkey that is dramatically faster. In our tests, it executed the Sunspider benchmark nearly three times faster than Firefox 3.0, though not quite as fast as Google's Chrome. When it comes to DOM manipulation though, there was little improvement.

Firefox scores well against its rivals in memory usage. IE8 and Chrome use a new process for each tab, which eats memory. Informal tests suggest that Firefox uses less RAM even with just one page open, and its advantage grows as further tabs are opened. In a quick informal test, Firefox used about the same RAM as Safari. Only Opera was slimmer.

Good for users then, but no big deal. What about web development? This is where it gets interesting. On the Acid3 test, at which IE8 fails badly, Firefox 3.5 is nearly but not quite perfect. The new browser also implements a good chunk of HTML 5, including an enhanced Canvas element with a text API, audio and video elements, a simple local storage API, downloadable fonts (a CSS feature), and JavaScript threading using web workers. The underlying story is an effort to push developers away from Adobe Flash and Microsoft Silverlight and towards standard HTML, when implementing rich content, multimedia, and rich internet applications.

In this respect, Firefox 3.5 is more a statement of intent than a realistic alternative to Flash. The audio element only supports Ogg Vorbis or uncompressed wave audio, while video is limited to Ogg Theora.

Standards tussle

Adobe's Flash, by contrast, offers a consistent cross-browser runtime, integrated with its Creative Suite design tools that are used everywhere. It may be hard to convince Microsoft to implement standards that compete with Silverlight in IE. Still, it is a significant statement of intent, and a few years from now Adobe's hold on web multimedia may be less secure.

Another key question is whether Google, Mozilla, and Apple can avoid fragmentation of evolving standards. Google's Gears extension overlaps with much of what is in HTML 5.0, but has its own specification. Features like local SQL support are different in Safari and Chrome and not present at all in Firefox except for extensions.

When he worked at Google, Mozilla's Dion Almaer argued that: "HTML 5 and Gears will converge in the not too distant path." They need to. Otherwise, both will be undermined.

Existing users will find Firefox 3.5 solid though unexciting and will stick with it - if only for the sake of its rich library of add-ons, which are now its main advantage over Safari and Chrome. Developers will like the TraceMonkey JavaScript engine along with more bits of HTML 5.0.

In summary: a good release, which increases the pressure on Microsoft's IE. ®

Secure remote control for conventional and virtual desktops

More from The Register

next story
Microsoft WINDOWS 10: Seven ATE Nine. Or Eight did really
Windows NEIN skipped, tech preview due out on Wednesday
Business is back, baby! Hasta la VISTA, Win 8... Oh, yeah, Windows 9
Forget touchscreen millennials, Microsoft goes for mouse crowd
Apple: SO sorry for the iOS 8.0.1 UPDATE BUNGLE HORROR
Apple kills 'upgrade'. Hey, Microsoft. You sure you want to be like these guys?
ARM gives Internet of Things a piece of its mind – the Cortex-M7
32-bit core packs some DSP for VIP IoT CPU LOL
Microsoft on the Threshold of a new name for Windows next week
Rebranded OS reportedly set to be flung open by Redmond
Lotus Notes inventor Ozzie invents app to talk to people on your phone
Imagine that. Startup floats with voice collab app for Win iPhone
'Google is NOT the gatekeeper to the web, as some claim'
Plus: 'Pretty sure iOS 8.0.2 will just turn the iPhone into a fax machine'
prev story

Whitepapers

Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.
The next step in data security
With recent increased privacy concerns and computers becoming more powerful, the chance of hackers being able to crack smaller-sized RSA keys increases.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.