In December 2015, Mozilla announced that its ambitious new operating system would not be appearing on any new phones, but the project may still live on as a platform for smart TVs and IoT devices.
The mobile device space is dominated by two platforms: Apple's iOS and Google's Android. Is there space for another platform? If you asked Mozilla a year ago, the answer would have been an emphatic yes. Inspired by Chrome OS, Mozilla imagined a platform where apps were essentially Web sites. That dream became a reality in Firefox OS.
The idea isn't new. Cordova is an open-source project that uses Web technologies to build cross-platform apps. The same code base can be deployed to Android devices, iPhones and even Windows PCs. The main difference is that Firefox OS offers native support for HTML5 Web apps. This makes the development and deployment process simpler, and it provides a rich device API for developers to use.
There's no doubt that Firefox OS's lightweight Web-centric design makes it an appealing platform for developers. The browser-based stack makes it easy to develop new applications rapidly, reusing code from existing projects and third-party libraries.
But, pleasing developers is only one part of the puzzle. To succeed in the competitive mobile platform space, Mozilla would need to convince handset manufacturers to support its product. It also would need to demonstrate that the new platform offered benefits that aren't available in Android. And, Mozilla would need to convince users as well.
Although HTML5 app development is possible on Android and iOS, most developers use the native frameworks instead. Those frameworks are more complex and less portable than HTML5. So, why is the native framework the preferred choice? The main reason is performance. The native frameworks offer greater performance by hooking into low-level libraries. These libraries are optimized for performance on mobile hardware, offering a fast and responsive user experience.
The root of the problem is the browser itself. Web browsers are built to accommodate a wide range of different types of content and layouts. That flexibility comes at a cost. In the case of Web browsers, that cost comes in the form of the DOM.
The DOM is the "Document Object Model", a data structure that represents the structure of the page. The DOM is expensive--it's memory-heavy. Rendering the DOM (turning it into an image) is computationally expensive as well. Web applications work by manipulating the DOM. Each small change requires a number of recalculations and layout changes. Each of those changes chews up processor power, so HTML5 apps seem less responsive because their runtime engine has to work harder to process changes to the display.
In the end, it's this performance bottleneck that keeps HTML5 from replacing native frameworks. Developers rely on the native frameworks instead.
On Firefox OS, there is no other framework. HTML5 apps are the only option. As a result, even simple Firefox apps struggle to match the performance of apps on Android devices.
Selling Firefox OS to mobile handset manufacturers has been a slow and painful process, and Mozilla is calling it a day, but it isn't quite giving up on its baby yet.
Firefox OS has demonstrated that it's a very flexible platform. It has the potential to run on a wide range of devices, such as TVs and IoT gadgets. As long as Mozilla can find some persuasive use cases for manufacturers, it has a good chance of making an impact in these emerging fields.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Google's SwiftShader Released
- Interview with Patrick Volkerding
- SUSE LLC's SUSE Manager
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Returning Values from Bash Functions
- SuperTuxKart 0.9.2 Released
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide