The Dawn of a Post-Gates, Post-Microsoft World
The depth of Microsoft loathing among our clan is perhaps only second to our penguin loving. This loathing makes sense, given that Linux and open-source people are so fiercely merit driven, and great products have failed to end Microsoft's hegemony. But times they are a changin', for a post-Gates, post-Microsoft age has already begun.
This week's media have been filled with news about Bill Gates going on a 'permanent sabbatical' of sorts from his duties as Microsoft's chairman. This move is interesting in two ways.
First, Gates will spend even more of his efforts on the Bill and Melinda Gates Foundation, which is positive thing. He's working on important health and education issues in very poor countries. As long as Gates doesn't aim to bring the same hegemonic practices to philanthropy as he has to computing, his decision is probably positive for the world.
Second, Gates' departure may mean that the era of fat-client, monopolist-dominant computing has reached a new phase of decline. He has done his work, and it's time to pass the baton off to someone else. Gates has performed this handoff to Steve Ballmer, but, the reality is that Ballmer is cut from the same cloth as Gates and therefore is a status quo man in many ways.
That Ballmer is at the helm of Microsoft with a business-as-usual approach make Microsoft's eventual decline seem inevitable. The company's antics - FUD propaganda towards Linux and open source, foot dragging on interoperability, intentional trashing of open standards, pathetic bloatware like Windows Vista, seeking to buy its way into the Internet age via Yahoo! - show that it is looking backward rather than forwards. In many ways, companies like Google have made Microsoft's products either irrelevant or less important. Today it's Google, Apple's devices, Firefox and Ubuntu that own the zeitgeist of our current computing age - not Microsoft.
Microsoft's zenith was the release of Windows XP. The subsequent years have been almost solely a string of security breaches and misfires.
Could Microsoft regain the momentum it had in the 1980s and 1990s? Because of the dynamics of organizations, I would argue 'no'. It does seem that most organizations indeed run a course from growth to maturity and finally to decline. One might argue that a company like IBM, which went through such a huge restructuring - who would have thought IBM would be one of Linux's biggest boosters! - is an example of how an organization can rebound from a decline. Still, although IBM is a great powerhouse, today it does not have the same society-driving influence that it once had.
What is Microsoft's fate, post Gates? If Ballmer is in charge, look for more decline, because he's business as usual. The company probably has to hit some kind of 'rock bottom' before it makes real change. We may not be close to a hard thud yet, but it seems that the fate is inevitable one day.
At least we Linuxers can rejoice in the fact that the day of reckoning, when merit does matter, may not be here, but that glorious day appears closer as Microsoft bids its founder adieu.
James Gray is Products Editor for Linux Journal.
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|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader 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