Ruby: Productive Programming Language
For raw performance, C/C++ is still the best choice. For large multiplatform team efforts you may be best off with Java. But when it comes to delivering speed and proof-of-concepts, you should think seriously about using Python or Ruby. Perl I would reserve for system administration tasks.
Ruby has some distinct advantages over Python. It is a far cleaner OOP language with excellent features, and it supports Perl's regex type terse notation. It also scores high in enabling one to write short concise and maintainable code. In fact I do most of my development in Ruby now, touching Java and C++ only when I have to.
Ruby may not be a new paradigm, nor represent a new generation, but it combines the best of many programming languages and takes productivity to a new level. I am not original in stating that Ruby may supersede both Perl and Python and will make many a Java programmer envious.
Programming Ruby by David Thomas and Andrew Hunt, Addison-Wesley, October 2000, ISBN: 0201710897. Also on-line at www.rubycentral.com/book.
Ruby in a Nutshell by Yukihiro Matsumoto, November 2001, ISBN 0-59600-214-9. See www.oreilly.com/catalog/ruby for more information.
The Ruby Language web site is www.ruby-lang.org/en/.
The Ruby Application Archive contains many libraries and bindings and can be found at www.ruby-lang.org/en/raa.html/.
The pragmatic programmers are at www.pragmaticprogrammer.com/ruby/.
The C++ Programming Language, Bjarne Stroustrup, Addison-Wesley; ISBN: 0201700735
Pjotr Prins is senior developer for Causeway Technologies and has a real passion for development. He is convinced of the lower cost of maintenance of Linux systems (deploying some 30 ROCK Linux servers), Editor-in-Chief for the EUP E-zine and contributor to ROCK Linux and other open-source projects.
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
- Tech Tip: Really Simple HTTP Server with Python
- Returning Values from Bash Functions
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Rogue Wave Software's Zend Server
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
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