Personally, I have 2 use cases for Ruby:
Service Scenarios . I have many tasks at work that I would classify as "service." These tasks range from manipulating data from an Excel spreadsheet and importing into a SQL Server database to clean up a directory full of files, to create test data that I don’t want to create manually. Some of these scripts are quick 10-line scripts, and some of them apply to small applications, which I use quite often.
There are a few things that make Ruby really enjoyable for this:
It is very easy to start with a script. Tools like Rake are for organizing tasks, and I don’t need to create a bunch of extra frames to get started.
Libraries I know that other languages may have excellent libraries, but so far the Ruby libraries have suited my needs. And RubyGems makes it easy to install the library without having to manually download and install it.
Ruby has many built-in functions that make reading and processing files very easy.
DSLs . There are many tasks that are repeated and amenable to the creation of domain languages. Ruby has a very flexible syntax and has some functional aspects that give you more flexibility in how you write your programs. Often you can combine common functions in a DSL that suits your task.
Another thing I use Ruby for (to a lesser extent) is web development . The Ruby on Rails framework is what I mostly used, but I played a little with Merb before announcing a merge with Ruby on Rails.
I like Ruby on Rails for all the reasons I like Ruby. In fact, these are mainly Ruby features that make Ruby on Rails great. Rails itself is a domain-specific language written in Ruby, which makes web development a lot more fun (in my opinion) and faster.
I think a lot of people have the same attitude towards Ruby, and the community still seems very active and vibrant. I think this is a great language to learn what will be used for quite some time.
Matt ephraim
source share