Looking Ahead at Ruby in 2007
Last week, I looked back at Ruby in 2006. This week, it's time to look ahead. Here are 10 Ruby things I think are going to be hot in 2007:
- Refactoring tools — This is something I think there's just too much clamor for (and too much momentum toward) not to hit in 2007. The JRuby team is making steady progress in NetBeans and Eclipse while wierd, wonderful things are being done with code rewriting on top of ParseTree and other tools. This year, we'll be able to stop saying "Yeah, there aren't any tools, but Ruby is still really easy to refactor."
- YARV — It has already been merged into the Ruby's development tree, now's the time to see it stabilize and speed up.
- RSpec — RSpec is growing in popularity too. Recently people have asked if it should be included in the Ruby Standard Library (no, probably not), which certainly points to it's popularity. Even the rubinius hackers (see below) are using RSpec to write tests.
- JRuby — Ruby on the JVM picked up a lot of steam last year, and looks like it's just going to accelerate in 2007. I think it will help bring Ruby into a lot of Java shops, both as an excuse to run Ruby ("Hey, look it's on the JVM. We can still pretend it's Java") and as a vector for cool stuff like RSpec.
- rubinius — While it might not have the fresh new enterprise smell that JRuby does, rubinius is a pretty sweet project as well. It's already gaining a lot of visibility in the Ruby world, and once regular Ruby apps start running on it, I think we'll see it take off.
- a Ruby spec — Perhaps the biggest benefit we'll see from rubinius and JRuby is a real spec for Ruby 1.8 (and a test suite to ensure compatibility). This has been a knock against Ruby for a while, and 2007 should be the year the community answers it.
- more than just Ruby on Rails — 2007 will be the year other Ruby based web frameworks get a bit of the spotlight. Nitro, IOWA and others might not draw as many developers as Ruby on Rails has, but they will influence the Ruby web development landscape.
- Rake — is a great DSL for build management. Rake is alread moving forward on the JRuby platform, and others will see how useful it can be in 2007.
- RubyConf 2007 (in Toronto?) — RubyConf 2006 was a huge success, and in 2007 should be even bigger (I just hope I can get a ticket before they sell out). With all the cool things going on in the Ruby world already, RubyConf 2007 should be a Ruby hackers dream!
- regional conferences — Since not everyone will make it into RubyConf 2007, regional conferences like MountainWest RubyConf and the Gotham City Ruby Conf will step up to fill the void. This year, I expect to see a handful of great regional conferences show up.
So, what do you see in your crystal ball?
-- -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
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- 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