Open Source Being Repositioned in Corporate America
Open Source methodology has gained some ground in one of the last places you and I might expect: In the development area of corporations. Consultants are calling environments like Sourceforge Enterprise Edition a Digital Development Environment.
What about CVS and Subversion? They call that a code collaborative. Well, what about the developer's itch? That's now the sponsor's charter.
How long will it take for the new moniker of Digital Development Environment (DDE) to replace the term Open Source? I might assert that your guess isn't as good as mine. I don't mean that in an arrogant way. I just happen to live in that part of the consulting world where CIOs and Directors want to reposition OSS terms that scare their subordinates.
The term DDE appears is more digestible. CIO and directors are calling OSS methodology the new paradigm; it's something that IT workers expect as the world shifts away from analog development cycles to digital ones.
I anticipate that Open Source adoption will accelerate rapidly under the new moniker of DDE. If you think about it in terms of positioning, the term Open Source isn't needed in an enterprise.
One bright spot does exist in this "adopt and extend" model. If you consult, the companies engaged in changing their paradigms need you. They need a DDE consultant to teach them how to do Open Source development. Go figure.
Tom Adelstein currently works as a contract technical writer in the Information Technology Field. In March 2007, his latest O'Reilly Book, Linux System Administration was released. Tom's home web site Open Source Today has tips and techniques for system administrators and Open Source VARs.
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!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
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