Language Selection

English French German Italian Portuguese Spanish

The Mozilla Interview: Why Firefox Matters

Filed under
Interviews
Moz/FF

We had a chance to chat with Johnathan Nightingale Mozilla’s Director of Firefox Engineering about Firefox’ current challenges, its opportunities, its rivals, trends and its future.

Mozilla’s Firefox experienced a pretty rapid turn of fortunes last year and is still dealing with the effects of a changing browser landscape today. The rise of Chrome, a more competitive Microsoft, an increasingly loyal Apple user base, the often-delayed release of Firefox 4, created a perfect storm against Mozilla that is affecting its market share and credibility. Johnathan Nightingale agreed to spend some time with us to talk about the current state of Firefox and its immediate future in a very competitive environment.

As spokesperson for Mozilla and as Director of Firefox Engineering, Johnathan Nightingale is one of the most influential people at Mozilla as far as the future of the Firefox browser is concerned. He has been working for Mozilla since 2007.

rest here




Also: Google, Mozilla Team Up to Create a Smarter, Action-Based Web

More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more