Rubinius Tab Sweep
Ola Bini has written a couple of posts that touch on Rubinius and the other Ruby implementations. The first talks about the new weekly meeting of implementors, saying “[I]t’s a huge deal. This will make the lives of all Ruby implementations much easier, and the meeting yesterday actually accomplished some very nice things.” I hope we’ll see this yield more Ruby Implementor Summits and the like.
Ola also wrote about the RbYAML Project for the Google Summer of Code. As the RubyCentral organizer for the GSoC, I’m really excited that we have nine great looking projects (including RbYAML) that will really help the whole Ruby community.
Vladimir Sizikov wrote about the RubySpecs Project (an outgrowth of the Rubinius project). This one also tied into GSoC, we’ve got two students working on separate projects to improve spec coverage.
Charlie Nutter provided a good perspective on the various implementations. I’m not sure I agree with everything he says, but he’s a smaart guy and I don’t really want to bet against him either. Here’ the obligatory Rubinius quote:
Rubinius is, and always has been, a great project and a great idea. I talk with Evan and Brian and all the others on a daily basis, I contribute specs whenever I find gaps or fix bugs in JRuby, and I secretly harbor a desire to implement a JRuby/JVM backend for the Rubinius kernel. I’m sure we’ll see great things from Rubinius in the future.
Nikos Dimitrakopoulos provided some coverage of Ruby implementation performance. Rubinius doesn’t look to good, but the standard caveat still applies … they’re still focusing on completeness not performance.
Luis Lavena posted some surprising performance numbers for Rubinius. I think this is the first time I’ve ever seen Rubinius win a “shootout” with the Ruby 1.8.6. It might be a micro-benchmark, but I think som congratulations are in order.
-- -pate http://on-ruby.blogspot.com
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!
- Managing Linux Using Puppet
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
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