History

Early concept

Matsumoto has said that Ruby was conceived in 1993. In a 1999 post to the ruby-talk mailing list, he describes some of his early ideas about the language:[13]

I was talking with my colleague about the possibility of an object-oriented scripting language. I knew Perl (Perl4, not Perl5), but I didn't like it really, because it had the smell of a toy language (it still has). The object-oriented language seemed very promising. I knew Python then. But I didn't like it, because I didn't think it was a true object-oriented language – OO features appeared to be add-on to the language. As a language maniac and OO fan for 15 years, I really wanted a genuine object-oriented, easy-to-use scripting language. I looked for but couldn't find one. So I decided to make it.

Matsumoto describes the design of Ruby as being like a simple Lisp language at its core, with an object system like that of Smalltalk, blocks inspired by higher-order functions, and practical utility like that of Perl.[14]

The name "Ruby"

The name "Ruby" originated during an online chat session between Matsumoto and Keiju Ishitsuka on February 24, 1993, before any code had been written for the language.[15] Initially two names were proposed: "Coral" and "Ruby". Matsumoto chose the latter in a later e-mail to Ishitsuka.[16] Matsumoto later noted a factor in choosing the name "Ruby" - it was the birthstone of one of his colleagues.[17][18]

First publication

The first public release of Ruby 0.95 was announced on Japanese domestic newsgroups on December 21, 1995.[19][20] Subsequently, three more versions of Ruby were released in two days.[15] The release coincided with the launch of the Japanese-languageruby-list mailing list, which was the first mailing list for the new language.

In 1997, the first article about Ruby was published on the Web. In the same year, Matsumoto was hired by netlab.jp to work on Ruby as a full-time developer.[15]

In 1998, the Ruby Application Archive was launched by Matsumoto, along with a simple English-language homepage for Ruby.[15]

In 1999, the first English language mailing list ruby-talk began, which signaled a growing interest in the language outside Japan.[22] In this same year, Matsumoto and Keiju Ishitsuka wrote the first book on Ruby, The Object-oriented Scripting Language Ruby (??????????????? Ruby), which was published in Japan in October 1999. It would be followed in the early 2000s by around 20 books on Ruby published in Japanese.[15]

By 2000, Ruby was more popular than Python in Japan.[23] In September 2000, the first English language book Programming Ruby was printed, which was later freely released to the public, further widening the adoption of Ruby amongst English speakers. In early 2002, the English-language ruby-talk mailing list was receiving more messages than the Japanese-language ruby-list, demonstrating Ruby's increasing popularity in the non-Japanese speaking world.

Ruby 1.8

Ruby 1.8 was initially released August 2003, was stable for a long time, and was retired June 2013.[24] Although deprecated, there is still code based on it. Ruby 1.8 is only partially compatible with Ruby 1.9.

Around 2005, interest in the Ruby language surged in tandem with Ruby on Rails, a web framework written in Ruby. Rails is frequently credited with increasing awareness of Ruby.[28]

Ruby 1.9

Ruby 1.9 was released on Christmas Day in 2007. Effective with Ruby 1.9.3, released October 31, 2011,[29] Ruby switched from being dual-licensed under the Ruby License and the GPL to being dual-licensed under the Ruby License and the two-clause BSD license.[30] Adoption of 1.9 was slowed by changes from 1.8 that required many popular third party gems to be rewritten.

Ruby 2.0 is intended to be fully backward compatible with Ruby 1.9.3. As of the official 2.0.0 release on February 24, 2013, there were only five known (minor) incompatibilities.[34]

It has been obsolete since February 22, 2016,[35] and it will no longer receive bug and security fixes. Users are advised to upgrade to a more recent version.

Ruby 2.1

Ruby 2.1.0 was released on Christmas Day in 2013.[36] The release includes speed-ups, bugfixes, and library updates.

Starting with 2.1.0, Ruby's versioning policy is more like semantic versioning.[37] Although similar, Ruby's versioning policy is not compatible with semantic versioning:

Ruby

Semantic versioning

MAJOR: Increased when incompatible change which can't be released in MINOR. Reserved for special events.

MAJOR: Increased when you make incompatible API changes.

MINOR: increased every Christmas, may be API incompatible.

MINOR: increased when you add functionality in a backwards-compatible manner.

TEENY: security or bug fix which maintains API compatibility. May be increased more than 10 (such as 2.1.11), and will be released every 2-3 months.

PATCH: increased when you make backwards-compatible bug fixes.

PATCH: number of commits since last MINOR release (will be reset at 0 when releasing MINOR).

-

Semantic versioning also provides additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format, not available at Ruby.

Ruby 2.1 has been obsolete since April 1, 2017,[38] and it will no longer receive bug and security fixes. Users are advised to upgrade to a more recent version.

Ruby 2.2

Ruby 2.2.0 was released on Christmas Day in 2014.[39] The release includes speed-ups, bugfixes, and library updates and removes some deprecated APIs. Most notably, Ruby 2.2.0 introduces changes to memory handling – an incremental garbage collector, support for garbage collection of symbols and the option to compile directly against jemalloc. It also contains experimental support for using vfork(2) with system and spawn, and added support for the Unicode 7.0 specification.

Features that were made obsolete or removed include callcc, the DL library, Digest::HMAC, lib/rational.rb, lib/complex.rb, GServer, Logger::Application as well as various C API functions.[40]

Ruby 2.3

Ruby 2.3.0 was released on Christmas Day in 2015. A few notable changes include:

The ability to mark all string literals as frozen by default with a consequently large performance increase in string operations.[45]

Hash comparison to allow direct checking of key/value pairs instead of just keys.

A new safe navigation operator&. that can ease nil handling (e.g. instead of ifobj&&obj.foo&&obj.foo.bar, we can use if obj&.foo&.bar).

The did_you_mean gem is now bundled by default and required on startup to automatically suggest similar name matches on a NameError or NoMethodError.

Hash#dig and Array#dig to easily extract deeply nested values (e.g. given profile={social:{wikipedia:{name:'Foo Baz'}}}, the value Foo Baz can now be retrieved by profile.dig(:social, :wikipedia, :name)).

.grep_v(regexp) which will match all negative examples of a given regular expression in addition to other new features.

The 2.3 branch also includes many performance improvements, updates, and bugfixes including changes to Proc#call, Socket and IO use of exception keywords, Thread#name handling, default passive Net::FTP connections, and Rake being removed from stdlib.[46]

Ruby 2.4

Ruby 2.4.0 was released on Christmas Day in 2016. A few notable changes include:

Binding#irb: Start a REPL session similar to binding.pry

Unify Fixnum and Bignum into Integer class

String supports Unicode case mappings, not just ASCII

A new method, Regexp#match?, which is a faster boolean version of Regexp#match

Thread deadlock detection now shows threads with their backtrace and dependency

The 2.4 branch also includes performance improvements to hash table, Array#max, Array#min, and instance variable access.[47]

Ruby's popularity has been declining since 2014,[48] a slip that may be permanent in the face of increasing competition.[49]

Ruby 2.5

Ruby 2.5.0 was released on Christmas Day in 2017.[50] A few notable changes include:

Philosophy

Matsumoto has said that Ruby is designed for programmer productivity and fun, following the principles of good user interface design.[81] At a Google Tech Talk in 2008 Matsumoto further stated, "I hope to see Ruby help every programmer in the world to be productive, and to enjoy programming, and to be happy. That is the primary purpose of Ruby language."[82] He stresses that systems design needs to emphasize human, rather than computer, needs:[83]

Often people, especially computer engineers, focus on the machines. They think, "By doing this, the machine will run fast. By doing this, the machine will run more effectively. By doing this, the machine will something something something." They are focusing on machines. But in fact we need to focus on humans, on how humans care about doing programming or operating the application of the machines. We are the masters. They are the slaves.

Ruby is said to follow the principle of least astonishment (POLA), meaning that the language should behave in such a way as to minimize confusion for experienced users. Matsumoto has said his primary design goal was to make a language that he himself enjoyed using, by minimizing programmer work and possible confusion. He has said that he had not applied the principle of least astonishment to the design of Ruby,[83] but nevertheless the phrase has come to be closely associated with the Ruby programming language. The phrase has itself been a source of surprise, as novice users may take it to mean that Ruby's behaviors try to closely match behaviors familiar from other languages. In a May 2005 discussion on the newsgroup comp.lang.ruby, Matsumoto attempted to distance Ruby from POLA, explaining that because any design choice will be surprising to someone, he uses a personal standard in evaluating surprise. If that personal standard remains consistent, there would be few surprises for those familiar with the standard.[84]

Everyone has an individual background. Someone may come from Python, someone else may come from Perl, and they may be surprised by different aspects of the language. Then they come up to me and say, 'I was surprised by this feature of the language, so Ruby violates the principle of least surprise.' Wait. Wait. The principle of least surprise is not for you only. The principle of least surprise means principle of least my surprise. And it means the principle of least surprise after you learn Ruby very well. For example, I was a C++ programmer before I started designing Ruby. I programmed in C++ exclusively for two or three years. And after two years of C++ programming, it still surprises me.

Semantics

Ruby is object-oriented: every value is an object, including classes and instances of types that many other languages designate as primitives (such as integers, booleans, and "null"). Variables always hold references to objects. Every function is a method and methods are always called on an object. Methods defined at the top level scope become methods of the Object class. Since this class is an ancestor of every other class, such methods can be called on any object. They are also visible in all scopes, effectively serving as "global" procedures. Ruby supports inheritance with dynamic dispatch, mixins and singleton methods (belonging to, and defined for, a single instance rather than being defined on the class). Though Ruby does not support multiple inheritance, classes can import modules as mixins.

According to the Ruby FAQ, the syntax is similar to Perl and the semantics are similar to Smalltalk, but it differs greatly from Python.[93]

Syntax

The syntax of Ruby is broadly similar to that of Perl and Python. Class and method definitions are signaled by keywords, whereas code blocks can be both defined by keywords or braces. In contrast to Perl, variables are not obligatorily prefixed with a sigil. When used, the sigil changes the semantics of scope of the variable. For practical purposes there is no distinction between expressions and statements.[94][95] Line breaks are significant and taken as the end of a statement; a semicolon may be equivalently used. Unlike Python, indentation is not significant.

One of the differences from Python and Perl is that Ruby keeps all of its instance variables completely private to the class and only exposes them through accessor methods (attr_writer, attr_reader, etc.). Unlike the "getter" and "setter" methods of other languages like C++ or Java, accessor methods in Ruby can be created with a single line of code via metaprogramming; however, accessor methods can also be created in the traditional fashion of C++ and Java. As invocation of these methods does not require the use of parentheses, it is trivial to change an instance variable into a full function, without modifying a single line of calling code or having to do any refactoring achieving similar functionality to C# and VB.NET property members.

Python's property descriptors are similar, but come with a tradeoff in the development process. If one begins in Python by using a publicly exposed instance variable, and later changes the implementation to use a private instance variable exposed through a property descriptor, code internal to the class may need to be adjusted to use the private variable rather than the public property. Ruby's design forces all instance variables to be private, but also provides a simple way to declare set and get methods. This is in keeping with the idea that in Ruby, one never directly accesses the internal members of a class from outside the class; rather, one passes a message to the class and receives a response.

See the Examples section below for samples of code demonstrating Ruby syntax.

Interaction

The Ruby official distribution also includes irb, an interactive command-line interpreter that can be used to test code quickly. The following code fragment represents a sample session using irb:

# Everything, including a literal, is an object, so this works:-199.abs# => 199'ice is nice'.length# => 11'ruby is cool.'.index('u')# => 1"Nice Day Isn't It?".downcase.split('').uniq.sort.join# => " '?acdeinsty"

Input:

print'Please type name >'name=gets.chompputs"Hello #{name}."

Conversions:

puts'Give me a number'number=gets.chompputsnumber.to_ioutput_number=number.to_i+1putsoutput_number.to_s+' is a bigger number.'

Strings

There are a variety of ways to define strings in Ruby.

The following assignments are equivalent:

a="\nThis is a double-quoted string\n"a=%Q{\nThis is a double-quoted string\n}a=%{\nThis is a double-quoted string\n}a=%/\nThis is a double-quoted string\n/a=<<-BLOCKThis is a double-quoted stringBLOCK

# In an object instance variable (denoted with '@'), remember a block.defremember(&a_block)@block=a_blockend# Invoke the preceding method, giving it a block that takes a name.remember{|name|puts"Hello, #{name}!"}# Call the closure (note that this happens not to close over any free variables):@block.call('Jon')# => "Hello, Jon!"

defcreate_set_and_get(initial_value=0)# note the default value of 0closure_value=initial_value[Proc.new{|x|closure_value=x},Proc.new{closure_value}]endsetter,getter=create_set_and_get# returns two valuessetter.call(21)getter.call# => 21# Parameter variables can also be used as a binding for the closure,# so the preceding can be rewritten as:defcreate_set_and_get(closure_value=0)[proc{|x|closure_value=x},proc{closure_value}]end

Yielding the flow of program control to a block that was provided at calling time:

A method such as inject can accept both a parameter and a block. The inject method iterates over each member of a list, performing some function on it while retaining an aggregate. This is analogous to the foldl function in functional programming languages. For example:

[1,3,5].inject(10){|sum,element|sum+element}# => 19

On the first pass, the block receives 10 (the argument to inject) as sum, and 1 (the first element of the array) as element. This returns 11, which then becomes sum on the next pass. It is added to 3 to get 14, which is then added to 5 on the third pass, to finally return 19.

Using an enumeration and a block to square the numbers 1 to 10 (using a range):

(1..10).collect{|x|x*x}# => [1, 4, 9, 16, 25, 36, 49, 64, 81, 100]

Or invoke a method on each item (map is a synonym for collect):

(1..5).map(&:to_f)# => [1.0, 2.0, 3.0, 4.0, 5.0]

Classes

The following code defines a class named Person. In addition to initialize, the usual constructor to create new objects, it has two methods: one to override the <=> comparison operator (so Array#sort can sort by age) and the other to override the to_s method (so Kernel#puts can format its output). Here, attr_reader is an example of metaprogramming in Ruby: attr_accessor defines getter and setter methods of instance variables, but attr_reader only getter methods. The last evaluated statement in a method is its return value, allowing the omission of an explicit return statement.

Open classes

In Ruby, classes are never closed: methods can always be added to an existing class. This applies to all classes, including the standard, built-in classes. All that is needed to do is open up a class definition for an existing class, and the new contents specified will be added to the existing contents. A simple example of adding a new method to the standard library's Time class:

Adding methods to previously defined classes is often called monkey-patching. If performed recklessly, the practice can lead to both behavior collisions with subsequent unexpected results and code scalability problems.

Since Ruby 2.0 it has been possible to use refinements to reduce the potentially negative consequences of monkey-patching, by limiting the scope of the patch to particular areas of the code base.

# re-open Ruby's Time classmoduleRelativeTimeExtensionsrefineTimedodefhalf_a_day_agoself-43200endendendmoduleMyModuleclassMyClass# Allow the refinement to be usedusingRelativeTimeExtensionsdefwindowTime.now.half_a_day_agoendendend

Exceptions

An exception is raised with a raise call:

raise

An optional message can be added to the exception:

raise"This is a message"

Exceptions can also be specified by the programmer:

raiseArgumentError,"Illegal arguments!"

Alternatively, an exception instance can be passed to the raise method:

raiseArgumentError.new("Illegal arguments!")

This last construct is useful when raising an instance of a custom exception class featuring a constructor that takes more than one argument:

classParseError<Exceptiondefinitialize(input,line,pos)super"Could not parse '#{input}' at line #{line}, position #{pos}"endendraiseParseError.new("Foo",3,9)

Exceptions are handled by the rescue clause. Such a clause can catch exceptions that inherit from StandardError. Other flow control keywords that can be used when handling exceptions are else and ensure:

begin# do somethingrescue# handle exceptionelse# do this if no exception was raisedensure# do this whether or not an exception was raisedend

It is a common mistake to attempt to catch all exceptions with a simple rescue clause. To catch all exceptions one must write:

begin# do somethingrescueException# Exception handling code here.# Don't write only "rescue"; that only catches StandardError, a subclass of Exception.end

Or catch particular exceptions:

begin# do somethingrescueRuntimeError# handle only RuntimeError and its subclassesend

It is also possible to specify that the exception object be made available to the handler clause:

Metaprogramming

Ruby code can programmatically modify, at runtime, aspects of its own structure that would be fixed in more rigid languages, such as class and method definitions. This sort of metaprogramming can be used to write more concise code and effectively extend the language.

For example, the following Ruby code generates new methods for the built-in String class, based on a list of colors. The methods wrap the contents of the string with an HTML tag styled with the respective color.

Starting with Ruby 1.9, and continuing with Ruby 2.x and above, the official Ruby interpreter has been YARV ("Yet Another Ruby VM"), and this implementation has superseded the slower virtual machine used in previous releases of MRI.

TruffleRuby, a Java implementation using the Truffle language implementation framework with GraalVM

Rubinius, a C++ bytecode virtual machine that uses LLVM to compile to machine code at runtime. The bytecode compiler and most core classes are written in pure Ruby. Rubinius currently targets Ruby 2.1,

The maturity of Ruby implementations tends to be measured by their ability to run the Ruby on Rails (Rails) framework, because it is complex to implement and uses many Ruby-specific features. The point when a particular implementation achieves this goal is called "the Rails singularity". The reference implementation (MRI), JRuby, and Rubinius[97] are all able to run Rails unmodified in a production environment.

Repositories and libraries

RubyGems is Ruby's package manager. A Ruby package is called a "gem" and can easily be installed via the command line. Most gems are libraries, though a few exist that are applications, such as IDEs.[102] There are over 9,000 Ruby gems hosted on RubyGems.org.

Many new and existing Ruby libraries are hosted on GitHub, a service that offers version control repository hosting for Git.

The Ruby Application Archive, which hosted applications, documentation, and libraries for Ruby programming, was maintained until 2013, when its function was transferred to RubyGems.[103]

^Lattner, Chris (2014-06-03). "Chris Lattner's Homepage". Chris Lattner. Retrieved . The Swift language is the product of tireless effort from a team of language experts, documentation gurus, compiler optimization ninjas, and an incredibly important internal dogfooding group who provided feedback to help refine and battle-test ideas. Of course, it also greatly benefited from the experiences hard-won by many other languages in the field, drawing ideas from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list.

Manage research, learning and skills at IT1me. Create an account using LinkedIn to manage and organize your IT knowledge. IT1me works like a shopping cart for information -- helping you to save, discuss and share.

Manage research, learning and skills at IT1me. Create an account using LinkedIn to manage and organize your IT knowledge. IT1me works like a shopping cart for information -- helping you to save, discuss and share.