Firefox Mimics Chrome: New Updates Explained
Firefox's Upcoming Architectural Shifts
Significant modifications are anticipated for Mozilla Firefox in the near future. Before the close of 2015, Firefox is scheduled to transition to a multi-process architecture, mirroring that of Google Chrome.
Furthermore, within a timeframe of one to one and a half years, Firefox intends to discontinue its existing add-on framework.
Transition to Chrome-Compatible Extensions
The current system will be replaced with one exhibiting substantial compatibility with Chrome extensions. This represents a considerable shift in Firefox’s approach to extensibility.
Implications of the Changes
While these alterations aren't inherently negative – and could be considered substantial enhancements – they do signal a move away from Firefox’s unique characteristics.
Firefox appears to be relinquishing a key differentiator, increasingly aligning itself with its primary competitor. Consequently, the rationale for choosing Firefox over Chrome is becoming less pronounced.
A Shrinking List of Advantages
The factors that previously distinguished Firefox are diminishing in number. This shift raises questions about the browser’s future identity and competitive positioning.
The move towards compatibility with Chrome extensions is expected to streamline development and broaden the availability of browser enhancements.
However, it also means Firefox is sacrificing some of its independence in the browser ecosystem.
The Imminent Arrival of Multi-Process, Sandboxed Firefox
Currently, Firefox uniquely operates as a predominantly single-process web browser. Other major browsers, including Chrome, Internet Explorer, Microsoft Edge, Safari, and Opera, all utilize a multi-process architecture.
It's important to note that Firefox isn't entirely single-process; it employs a dedicated plugin-container process for isolating plugins like Flash. However, even with a powerful multi-core processor, multiple web pages won't be distributed across those cores – they remain confined to a single core.
Related: Understanding Firefox's Lag Behind Google Chrome
Mozilla has been developing a project called Electrolysis to address this limitation. Initial efforts were suspended in 2011 due to technical challenges, but the project was later revived. Fortunately, its completion is now within reach. Multi-process Firefox is enabled by default in the latest nightly builds and is scheduled for general release in mid-December 2015, as announced by Mozilla.
This update will allow Firefox to effectively leverage multi-core CPUs for improved performance when handling numerous web pages simultaneously.
Furthermore, the implementation of security sandboxing will coincide with Electrolysis. This feature, long available in other browsers – including Internet Explorer – has been a significant omission in Firefox. Currently, Firefox is the only major browser lacking sandboxing technologies to mitigate the potential damage from browser-based exploits.
This deficiency has had tangible consequences, as demonstrated by a recent malvertising incident. A zero-day vulnerability in Firefox was exploited to compromise users of Windows, macOS, and Linux through a Russian website. Sandboxing could have prevented this attack, or at least necessitated an additional exploit targeting the sandbox itself.
Firefox Transitions to WebExtensions: A Shift in Extension Frameworks
Mozilla has recently declared its plans to phase out the existing Firefox extension framework in favor of a new system. This forthcoming framework, known as WebExtensions, demonstrates "substantial compatibility with the models utilized by Chrome and Opera." Microsoft Edge is also preparing to adopt a similar extension framework aligned with Chrome’s, with Apple being a notable exception to this trend.
The current extensions built on XUL and XPCOM technologies will be deprecated and ultimately removed within approximately eighteen months. Consequently, the robust add-ons currently employed by Firefox users will eventually be discontinued, giving way to add-ons more akin to those found in Chrome.
Addressing Concerns and Future Development
This change doesn’t signify a negative outcome. Mozilla aims to leverage the Chrome extensions framework while incorporating enhancements to enable functionalities like NoScript and sidebar integration, mirroring features available in Opera. The company is dedicated to ensuring the continued operation of widely-used extensions within the evolving Firefox environment.
Furthermore, this transition is viewed positively. Firefox’s existing extension framework has presented challenges, particularly with the introduction of a rapid release cycle. It is anticipated to create further complications, as many extensions will require updates to maintain compatibility with multi-process Firefox.
Future projects, such as Servo – a potential replacement for the Gecko layout engine – would also be incompatible with the older extension system. An improvement in security is also expected, as extensions will benefit from increased sandboxing and restricted access to system resources.
The Trade-offs of Standardization
However, this shift understandably causes concern among some users. The new system will result in a less powerful extension framework for Firefox. Currently, browser extensions possess extensive capabilities within Firefox.
While this can lead to security vulnerabilities, compatibility problems, and development issues, it also represents Firefox’s key differentiator – offering the most powerful add-on framework available. This advantage is poised to diminish.
Mozilla intends to implement features that will allow popular add-ons to remain functional, but less frequently used and future add-ons will face greater limitations in their capabilities.
The loss of the most powerful add-on framework would eliminate a significant competitive advantage for Firefox.
- The current XUL and XPCOM extensions will be phased out.
- WebExtensions offer compatibility with Chrome and Opera.
- Security and compatibility are key drivers for the change.
For Years, Firefox Has Mirrored Chrome’s DevelopmentIt’s evident that Firefox has consistently adopted strategies pioneered by Chrome. Following Chrome’s initial release, Mozilla implemented a swift release schedule, delivering Firefox updates every six weeks. This accelerated pace, however, introduced compatibility issues with existing add-ons, as the Firefox add-on framework wasn’t initially structured to support such frequent changes.
In the previous year, Firefox introduced a new visual theme, Australis, intended to present a more contemporary appearance. A significant portion of the user base perceived this design as heavily influenced by Chrome and expressed dissatisfaction with it. Furthermore, Firefox has also removed the status bar, mirroring a similar decision made by Chrome.
The similarities extend to other functionalities as well. Firefox Sync underwent a redesign, shifting to a simpler username and password authentication system, much like Chrome’s approach. Users can now simultaneously utilize standard and private browsing modes, a feature also found in Chrome. Mozilla has begun integrating features of debatable value, such as Firefox Hello and Pocket integration, echoing Google’s practice of embedding its own services within Chrome.
H.264 video playback is now supported within Firefox, aligning it with the capabilities of other major browsers.
Mozilla is also enacting a policy restricting add-on installations on the stable Firefox version to those digitally signed by Mozilla. Users desiring to install unsigned add-ons will be required to switch to a developer version. This measure, implemented for security purposes, parallels a similar restriction in Chrome.
Moreover, Mozilla is preparing to launch Firefox for iOS – a browser designed for iPhones and iPads. This version utilizes Apple’s Safari rendering engine but enables synchronization with a user’s Firefox account. Chrome for iOS operates in a comparable manner, although Mozilla previously refrained from this approach due to limitations preventing the use of their proprietary Gecko rendering engine.
The Erosion of Firefox's Unique Character
It’s important to state upfront that many of the recent alterations implemented within Firefox are, in themselves, positive developments. Even modifications that have sparked debate, such as the phasing out of the existing extension framework, are likely to yield benefits over time.
However, a concerning trend is becoming increasingly apparent: Firefox is steadily diminishing its individual characteristics. The decision to replace its robust extension framework with an add-on system largely mirroring Chrome’s will significantly impact a dedicated segment of Firefox users.
A crucial inquiry Mozilla must address is this: What compelling reasons exist for a user to choose Firefox over Chrome? The organization likely emphasizes its non-profit status and commitment to web betterment, contrasting with the profit-driven motives of its competitors.
Furthermore, Firefox utilizes Gecko, a distinct rendering engine, which ideally contributes to the maintenance of web standards through diverse implementations. But the question remains – is this differentiation sufficient?
Currently, Firefox defaults to Yahoo as its primary search engine, a choice that offers little competitive advantage. A direct comparison illustrates the disparity: searching for "vlc" on Google, Bing, and Yahoo reveals significant differences.
Google prominently displays a direct download link for VLC, free from deceptive advertising. Bing presents potentially misleading ads but still guides users to the official VLC download page. Conversely, Yahoo inundates users with advertisements promoting malware, obscuring a clear path to the legitimate VLC download.
Consequently, Firefox currently possesses the least advantageous default search engine among major browsers, and Mozilla’s partnership with Yahoo does little to improve the user experience in this regard.