![]() ![]() We are working with the Platform team on technology platform futures too, and we're excited about the Gecko and Servo-based futures being discussed!" Mozilla's CTO also reaffirmed the company's commitment to the Gecko rendering engine: However, Mayo updated his post to say that "I should have been clearer that Project Tofino is wholly focused on UX explorations and not the technology platform. The biggest surprise, however, was that the project, named Tofino, will not use Firefox's core technology – Gecko – but will instead plumb for Electron, which is built on the technology behind Google's rival Chrome browser, called Chromium. "The premise for these experiments couldn't be simpler: what we need a browser to do for us – both on PCs and mobile devices – has changed a lot since Firefox 1.0, and we're long overdue for some fresh approaches." ![]() "Let's jump right in and say yes, the rumors are true, we're working on browser prototypes that look and feel almost nothing like the current Firefox," Mayo wrote in a blog post. ![]() Senior VP Mark Mayo caused a storm by revealing that the Firefox team is working on a next-generation browser that will run on the same technology as Google's Chrome browser. And, for the moment at least, it seems to lie in rival Chrome. ![]() The head of Mozilla's Firefox browser is looking to the future. Original Submission #1 Original Submission #2 Update: The Pale Moon developer named Al Billings as the Mozilla employee who contacted him ( submission). The web does still need Mozilla, but not as weak, uncertain and unnerved as they are right now. Hopefully Mozilla gets out of their downwards spiral soon. These moves are not helpful in restoring user faith in Mozilla and Firefox. Time is ticking and projects like Tofino add to the uncertainty about the future of Firefox ( Servo or Blink engine?), including the upcoming removal of XUL and the deprecation of the old add-on and theme model. Mozilla should also maintain healthier relationships with projects like Seamonkey and Thunderbird, which may lose users when Mozilla changes the user experience to be more Chrome-inspired. In conclusion, users hope that Mozilla stops their current quest to copy Google Chrome and move back in the direction of serving a tech-savvy user group which could allow them to regain a larger market share. If you are a big developer, one can argue that you should stand above incidents like that, but Mozilla's dwindling market share is putting them under heavier stress. It also looks like Mozilla has a growing animosity towards people taking and modifying the Mozilla source code for their own unique products, and they are also trying to get rid of projects which have been hosted and supported by Mozilla itself. The point is: Whether there are some rude comments by community members on a certain board or not, it seems like Mozilla employees are getting incredibly nervous because of their current peculiar state and are now unleashing their frustrations at the Pale Moon project. For example, this Mozilla employee mocking attempts to re-base Pale Moon and remove Australis, or as seen here where Mozilla guy Robert Kaiser accused the Pale Moon project of "destroying code and extorting money". This was not the only attack from Mozilla's side lately. But still, Mozilla seems to have had a real problem with the Pale Moon guys lately, and now appear to have demanded stricter moderation of the Pale Moon forums so that only favorable posts about Mozilla are published, or none at all. To date, there has been bad blood from Pale Moon community members in comments and forum posts that are dismissive of Mozilla, sometimes provocatively so. Those who are aware of the existence and goals of Pale Moon may have realized that there was a big nosedive in positive opinions of Firefox from both the Pale Moon maker and community when Mozilla changed their UX to Australis. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |