Don't Code for Linux
The days of developing applications for a single platform are history. Why? Because every platform offers at least one key benefit that cannot be attained on any other; Windows, Linux/UNIX, Mac OS X, embedded Linux and others each offer unique advantages. But given changing market conditions, it's impossible to predict which platform will give you the competitive edge you need.
Our anwser is: why pick? We feel that developers can and should leverage all the best qualities of each platform by embracing multiplatform development. This is true not only on the desktop, but also on the server, the network, mobile devices and every other tool that connects us. Our increasingly mobile working style demands portable data and portable applications to match today's distributed networks and global organizations.
Organizations that want to compete and survive must recognize a fragmented OS environment as a given, and they must respond by developing applications that run quickly, cleanly and natively on the greatest number of platforms possible. Applications written in this way take advantage of the best features each platform has to offer, without having to be written and rewritten for every instance. This process limits your company and represents a colossal waste of time. Forward-looking companies already recognize that single-platform development is destined to fail, and they have embraced a better way. Here's why we think this report on the death of single-platform development is not exaggerated.
If you wish to develop for more than one platform, thus expanding your target market, your costs rise dramatically. You need a full team to develop for each platform. Perhaps more importantly, you need a full team to maintain and support each platform. This represents a linear increase in cost for each platform—an extremely inefficient way to do business.
Developing applications for one platform increases your risk because you have to choose among markets before their potential is clear. Who's to say you'll be right? Software companies have been made or broken by this choice. In the recent past, people said Windows (with its momentum and market dominance) was the obvious choice—but wait! Linux has proven itself as a serious competitor in the server space and is picking up serious momentum on the desktop and in the embedded space. World-class consumer and enterprise companies are embracing its power, flexibility, security and low cost. So, what used to be an obvious platform decision isn't so obvious anymore. Do you know when (or where) this kind of rapid transformation will happen again? I don't.
Perhaps most importantly, if you limit development to a single desktop or server platform, you immediately restrict your access to the fastest-growing software market in the world: mobile systems. If, for example, you write an application for Microsoft Windows NT/2000, you automatically eliminate any cost-effective way to run your application on a mobile device, because you have to rewrite the source. Given that it's nearly essential to make applications mobile, developing applications on a single desktop/server platform can be a death sentence for that application even before it's finished.
The software industry has struggled for some time to develop commercially viable strategies for multiplatform development, and its history is littered with companies that have tried to do this, and failed. Why?
One difficulty has been a lack of complete functionality. Many toolkits deliver only subsets of functionality on multiple platforms, not the whole set. Another problem has been reliance on emulation or virtual machines. Both of these impose a significant and usually unacceptable performance penalty, especially for mobile devices that need high performance the most.
It's a well-recognized fact that differences between virtual machines lead to implementation workarounds and tweaks, as well as increased maintenance. This is another expense, and it makes the developers who have to do this work miserable.
Today, though, proven ways exist to write an application once, compile and run it anywhere. Companies who do multiplatform development create an environment in which development innovation will once again be the order of the day—not the exception.
Haavard Nord, cofounder and CEO of Trolltech, started his programming career trying to find acceptable multiplatform toolkits for database development. He now drives Trolltech's efforts in single-source, multiplatform software development. The company's products encourage innovation by letting developers write single-source applications that run natively on Windows, Linux, UNIX, Mac OS X and embedded Linux.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
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