This is definitely your papa's C++
A colleague of mine,he's old, not 100 old, actually he's closer to 50, but in IT, that's pretty old. And there's something I just don't understand, he loves C++.It's fairly common for people to have a pet programming language, which adapts to their particular desires and expectations of what a language should look like, this most often than not has more to do with their personality than actual technical prowess. A really practical guy like myself(or at least someone who thinks he is practical) loves PHP, Python and Ruby. Another colleague likes really ordered and structured things, he uses Java for most of his work. I even know a biker, boots, tattoos and all that uses smalltalk.
But this guy, when I ask him:"Papa(most of his ex-students call him that), why do you use C++?"
He just shrugs and says:"It's good,fast and gets the job done".
Now, C++ is a very powerful language, you have the world at your fingertips with it, memory management, 3D graphics, widgets, infinite libraries, fast, robust... Still many of my younger colleagues tend to avoid it, they avoid it with an almost pious observance, basking in its glory but afraid of touching it.
I know how to program in C++, I took some classes that only used C++, wanted to perform a lobotomy on myself with a paper clip and a gust of wind when I got mistakes from Visual C++ 6.0(In those dark times when I still used "That OS that can't be named"), switched to Bloodshed Dev C++, got scolded by one of my teachers for switching, she called me an "IDE whore".I even have copies of "Learn C++ through Game Programming" and "C++ How to program" from Deitel & Deitel, read them both.
Still, I always end up using other languages.
Maybe I'm just too plain old thick headed or took one too many tackles to my skull playing rugby.
I want your opinion, preferably if you earn a living as a Software Engineer, Programmer, Systems Administrator, Tech Guru or anything along these lines.
Should we call war on the old and pull the plug or embrace it like a good bodied, perfectly aged...cheese(smelly but delicious)?
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
- SourceClear Open
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