“Ruby (programming language)”的意思、由来-开放百科全书

reflective, object-oriented, general-purpose programming language. It was designed and developed in the mid-1990s by Yukihiro "Matz" Matsumoto in Japan.

According to the creator, Ruby was influenced by Perl, Smalltalk, Eiffel, Ada, and Lisp.^[11] It supports multiple programming paradigms, including functional, object-oriented, and imperative. It also has a dynamic type system and automatic memory management.

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:^[12]

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.^[13]

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.^[14] Initially two names were proposed: "Coral" and "Ruby". Matsumoto chose the latter in a later e-mail to Ishitsuka.^[15] Matsumoto later noted a factor in choosing the name "Ruby" – it was the birthstone of one of his colleagues.^[16]^[17]

First publication

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

Already present at this stage of development were many of the features familiar in later releases of Ruby, including object-oriented design, classes with inheritance, mixins, iterators, closures, exception handling and garbage collection.^[20]

Early releases

Following the release of Ruby 0.95 in 1995, several stable versions of Ruby were released in the following years:

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.^[14]

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

In 1999, the first English language mailing list ruby-talk began, which signaled a growing interest in the language outside Japan.^[21] 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.^[14]

By 2000, Ruby was more popular than Python in Japan.^[22] 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.^[35] Although deprecated, there is still code based on it. Ruby 1.8 is only partially compatible with Ruby 1.9.

Ruby 1.8 has been the subject of several industry standards. The language specifications for Ruby were developed by the Open Standards Promotion Center of the Information-Technology Promotion Agency (a Japanese government agency) for submission to the Japanese Industrial Standards Committee (JISC) and then to the International Organization for Standardization (ISO). It was accepted as a Japanese Industrial Standard (JIS X 3017) in 2011^[23] and an international standard (ISO/IEC 30170) in 2012.^[24]^[25]

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.^[26]

Ruby 1.9

Ruby 1.9 was released on Christmas Day in 2007. Effective with Ruby 1.9.3, released October 31, 2011,^[27] 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.^[28] Adoption of 1.9 was slowed by changes from 1.8 that required many popular third party gems to be rewritten.

Ruby 1.9 introduces many significant changes over the 1.8 series.^[29] Examples:

Ruby 1.9 has been obsolete since February 23, 2015,^[30] and it will no longer receive bug and security fixes. Users are advised to upgrade to a more recent version.

Ruby 2.0

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.^[32]

It has been obsolete since February 22, 2016,^[33] 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.^[34] The release includes speed-ups, bugfixes, and library updates.

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

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,^[36] 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.^[37] 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{{snd}} 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.^[38]

Ruby 2.3

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

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.^[44]

Ruby 2.4

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

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

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

Ruby 2.5

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

On top of that come a lot of performance improvements like faster block passing (3 times faster), faster Mutexes, faster ERB templates and improvements on some concatenation methods.

Ruby 2.6

Ruby 2.6.0 was released on Christmas Day in 2018.^[49] A few notable changes include:

Table of versions

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]

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]

Features

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.

Ruby has been described as a multi-paradigm programming language: it allows procedural programming (defining functions/variables outside classes makes them part of the root, 'self' Object), with object orientation (everything is an object) or functional programming (it has anonymous functions, closures, and continuations; statements all have values, and functions return the last evaluation). It has support for introspection, reflection and metaprogramming, as well as support for interpreter-based^[91] threads. Ruby features dynamic typing, and supports parametric polymorphism.

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

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.^[93]^[94] 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.

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:

Examples

The following examples can be run in a Ruby shell such as Interactive Ruby Shell, or saved in a file and run from the command line by typing ruby .

Strings

Collections

hash = { :water => 'wet', :fire => 'hot' } # makes the previous line redundant as we are now

hash.delete_if{|key,value| value == 'hot'} # deletes the pair :fire => 'hot' and returns {}

Control structures

Blocks and iterators

A code block can be passed to a method as an optional block argument. Many built-in methods have such arguments:

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:

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):

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.

Exceptions

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

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:

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

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.

To implement the equivalent in many other languages, the programmer would have to write each method (in_black, in_red, in_green, etc.) separately.

More examples

Implementations

Matz's Ruby interpreter

The original Ruby interpreter is often referred to as the Matz's Ruby Interpreter or MRI. This implementation is written in C and uses its own Ruby-specific virtual machine.

The standardized and retired Ruby 1.8 implementation was written in C, as a single-pass interpreted language.^[95]

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.

Alternate implementations

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.

Platform support

Matsumoto originally did Ruby development on the 4.3BSD-based Sony NEWS-OS 3.x, but later migrated his work to SunOS 4.x, and finally to Linux.^[98]^[99]

By 1999, Ruby was known to work across many different operating systems, including NEWS-OS, SunOS, AIX, SVR4, Solaris, NEC UP-UX, NeXTSTEP, BSD, Linux, Mac OS, DOS, Windows, and BeOS.^[100]

Modern Ruby versions and implementations are available on many operating systems, such as Linux, BSD, Solaris, AIX, macOS, Windows, Windows Phone,^[101] Windows CE, Symbian OS, BeOS, and IBM i.

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]

See also

References

1. ^{{cite web |url = http://ioke.org/ |title = Ioke |last = Bini |first = Ola |work = Ioke.org |accessdate = 2011-07-21 |quote = inspired by Io, Smalltalk, Lisp and Ruby |deadurl = yes |archiveurl = https://web.archive.org/web/20110721091046/http://www.ioke.org/ |archivedate = 2011-07-21 |df = }}
2. ^{{cite web |url=https://docs.julialang.org/en/stable/ |title=Julia 1.0 Documentation: Introduction |publisher= |accessdate=6 October 2018}}
3. ^{{cite web | url=http://programming.nu/about | title=About Nu™ | last=Burks | first=Tim | work=Programming Nu™ | publisher=Neon Design Technology, Inc. | accessdate=2011-07-21}}
4. ^{{cite web |url=http://ring-lang.sourceforge.net/doc1.6/introduction.html#ring-and-other-languages |title=Ring and other languages |author=Ring Team |date=3 December 2017 |work=ring-lang.net |publisher=ring-lang}}
5. ^{{cite web|url=http://nondot.org/sabre/|title=Chris Lattner's Homepage|last=Lattner|first=Chris|date=2014-06-03|accessdate=2014-06-03|publisher=Chris Lattner|quote=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.}}
6. ^{{cite web|url=https://svn.ruby-lang.org/cgi-bin/viewvc.cgi/trunk/COPYING?view=markup|title=[ruby] Contents of /trunk/COPYING|publisher=|accessdate=2 May 2015}}
7. ^{{cite web|url=https://svn.ruby-lang.org/cgi-bin/viewvc.cgi/trunk/GPL?view=markup|title=[ruby] Contents of /trunk/GPL|publisher=|accessdate=2 May 2015}}
8. ^{{cite web|url=https://svn.ruby-lang.org/cgi-bin/viewvc.cgi/trunk/BSDL?view=markup|title=[ruby] Contents of /trunk/BSDL|publisher=|accessdate=2 May 2015}}
9. ^¹²{{cite book | last=Cooper | first=Peter | title=Beginning Ruby: From Novice to Professional | edition=2nd | series=Beginning from Novice to Professional | year=2009 | publisher=APress | location=Berkeley | isbn=1-4302-2363-4 | page=101 | quote=To a lesser extent, Python, LISP, Eiffel, Ada, and C++ have also influenced Ruby.}}
10. ^¹²³⁴⁵{{cite book | last=Bini | first=Ola | title=Practical JRuby on Rails Web 2.0 Projects: Bringing Ruby on Rails to Java | year=2007 | publisher=APress | location=Berkeley | isbn=1-59059-881-4 | page=3 | quote=It draws primarily on features from Perl, Smalltalk, Python, Lisp, Dylan, and CLU.}}
11. ^{{cite web|url=https://www.ruby-lang.org/en/about/|title=About Ruby|accessdate=2 March 2014}}
12. ^{{cite web|url=https://www.ruby-doc.org/docs/ruby-doc-bundle/FAQ/FAQ.html|title=The Ruby Language FAQ|author=Shugo Maeda|date=17 December 2002|accessdate=2 March 2014}}
13. ^{{citation|url=http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/179642|title=ruby-talk: Re: Ruby's lisp features|author=Yukihiro Matsumoto|date=13 February 2006|accessdate=2 March 2014}}
14. ^¹²³⁴⁵{{cite web|url=http://blog.nicksieger.com/articles/2006/10/20/rubyconf-history-of-ruby|title=History of Ruby}}
15. ^{{cite web|url=http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/88819|title=[FYI: historic] The decisive moment of the language name Ruby. (Re: [ANN] ruby 1.8.1)|type=E-mail from Hiroshi Sugihara to ruby-talk}}
16. ^{{cite web | url=https://www.ruby-doc.org/docs/ruby-doc-bundle/FAQ/FAQ.html | title=The Ruby Language FAQ – 1.3 Why the name 'Ruby'? | publisher=Ruby-Doc.org | accessdate=April 10, 2012}}
17. ^{{cite mailing list | url=http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/394 | title=Re: the name of Ruby? | mailinglist=Ruby-Talk | date=June 11, 1999 | author=Yukihiro Matsumoto | accessdate=April 10, 2012}}
18. ^{{cite web|url=http://eigenclass.org/hiki/ruby+0.95|title=More archeolinguistics: unearthing proto-Ruby|publisher=|accessdate=2 May 2015|deadurl=yes|archiveurl=https://web.archive.org/web/20151106023204/http://eigenclass.org/hiki/ruby+0.95|archivedate=6 November 2015|df=}}
19. ^{{cite web|url=http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/382|title=[ruby-talk:00382] Re: history of ruby|publisher=|accessdate=2 May 2015}}
20. ^{{cite web|url=http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-list/124|title=[ruby-list:124] TUTORIAL - ruby's features|publisher=|accessdate=2 May 2015}}
21. ^{{cite web|url=http://www.linuxdevcenter.com/pub/a/linux/2001/11/29/ruby.html|title=An Interview with the Creator of Ruby}}
22. ^{{cite web|url=http://ruby-doc.com/docs/ProgrammingRuby/html/foreword.html|title=Programming Ruby: Forward|author=Yukihiro Matsumoto|date=October 2000|accessdate=5 March 2014}}
23. ^{{cite web|url=http://www.ipa.go.jp/about/press/20110322.html|title=IPA 独立行政法人情報処理推進機構：プレス発表　プログラム言語RubyのJIS規格（JIS X 3017）制定について|publisher=|accessdate=2 May 2015}}
24. ^{{cite web|url=http://www.ipa.go.jp/about/press/20120402_2.html|title=IPA 独立行政法人情報処理推進機構：プレス発表　プログラム言語Ruby、国際規格として承認|publisher=|accessdate=2 May 2015}}
25. ^{{cite web|url=https://www.iso.org/standard/59579.html|title=ISO/IEC 30170:2012|publisher=|accessdate=2017-03-10}}
26. ^Web Development: Ruby on Rails. Devarticles.com (2007-03-22). Retrieved on 2013-07-17.
27. ^{{cite web | title=Ruby 1.9.3 p0 is released | url=https://www.ruby-lang.org/en/news/2011/10/31/ruby-1-9-3-p0-is-released/ | publisher=ruby-lang.org | date=October 31, 2011 | accessdate=February 20, 2013}}
28. ^{{cite web | title=v1_9_3_0/NEWS | url=https://svn.ruby-lang.org/repos/ruby/tags/v1_9_3_0/NEWS | work=Ruby Subversion source repository | publisher=ruby-lang.org | date=September 17, 2011 | accessdate=February 20, 2013}}
29. ^Ruby 1.9: What to Expect. Slideshow.rubyforge.org. Retrieved on 2013-07-17.
30. ^{{cite web|url=https://www.ruby-lang.org/en/news/2015/02/23/support-for-ruby-1-9-3-has-ended/|title=Support for Ruby 1.9.3 has ended|publisher=|accessdate=2 May 2015}}
31. ^Endoh, Yusuke. (2013-02-24) [https://www.ruby-lang.org/en/news/2013/02/24/ruby-2-0-0-p0-is-released/ Ruby 2.0.0-p0 is released]. Ruby-lang.org. Retrieved on 2013-07-17.
32. ^Endoh, Yusuke. (2013-02-24) Ruby 2.0.0-p0 is released. Ruby-lang.org. Retrieved on 2013-07-17.
33. ^{{cite web|url=https://www.ruby-lang.org/en/news/2016/02/24/support-plan-of-ruby-2-0-0-and-2-1/|title=Support plans for Ruby 2.0.0 and Ruby 2.1|author=usa|publisher=Ruby-lang.org|date=2016-02-24|accessdate=2017-04-18}}
34. ^{{cite web| url=https://www.ruby-lang.org/en/news/2013/12/25/ruby-2-1-0-is-released/|title=Ruby 2.1.0 is released|date=December 25, 2013|accessdate=December 26, 2013}}
35. ^{{cite web| url=https://www.ruby-lang.org/en/news/2013/12/21/semantic-versioning-after-2-1-0/|title=Semantic Versioning starting with Ruby 2.1.0|date=December 21, 2013|accessdate=December 27, 2013}}
36. ^{{cite web|url=https://www.ruby-lang.org/en/news/2017/04/01/support-of-ruby-2-1-has-ended/|title=Support for Ruby 2.1 has ended|publisher=|accessdate=4 April 2017}}
37. ^{{cite web| url=https://www.ruby-lang.org/en/news/2014/12/25/ruby-2-2-0-released/|title=Ruby 2.2.0 Released|date=December 25, 2014|accessdate=January 4, 2015}}
38. ^{{cite web|url=https://github.com/ruby/ruby/blob/v2_2_0/NEWS|title=ruby/NEWS at v2_2_0 · ruby/ruby · GitHub|work=GitHub|accessdate=2 May 2015}}
39. ^{{cite web|url=https://www.ruby-lang.org/en/news/2015/03/03/ruby-2-2-1-released|title=Ruby 2.2.1 Released|accessdate=12 July 2016|author=Gustavo Frederico Temple Pedrosa, Vitor de Lima, Leonardo Bianconi|year=2015}}
40. ^{{cite web|url=https://svn.ruby-lang.org/repos/ruby/tags/v2_2_1/ChangeLog|title=v2.2.1 ChangeLog|accessdate=12 July 2016|author=Gustavo Frederico Temple Pedrosa, Vitor de Lima, Leonardo Bianconi|year=2015}}
41. ^{{cite web|url=https://bugs.ruby-lang.org/issues/9997|title=Specifying non volatile registers for increase performance in ppc64|accessdate=12 July 2016|author=Gustavo Frederico Temple Pedrosa, Vitor de Lima, Leonardo Bianconi|year=2014}}
42. ^{{cite web|url=https://bugs.ruby-lang.org/issues/10081|title=Specifying MACRO for increase performance in ppc64|accessdate=12 July 2016|author=Gustavo Frederico Temple Pedrosa, Vitor de Lima, Leonardo Bianconi|year=2014}}
43. ^{{cite web|url=http://dev.mensfeld.pl/2015/11/ruby-2-3-0-changes-and-features/#frozen|title=Ruby 2.3.0 changes and features - Running with Ruby|website=dev.mensfeld.pl}}
44. ^{{cite web|url=https://github.com/ruby/ruby/blob/v2_3_0/NEWS|title=Ruby/NEWS at v.2_3_0 - ruby/ruby - Github|work=GitHub|accessdate=25 December 2015}}
45. ^{{Cite web|url=https://www.ruby-lang.org/en/news/2016/12/25/ruby-2-4-0-released/|title=Ruby 2.4.0 Released|website=www.ruby-lang.org|access-date=2016-12-30}}
46. ^{{cite web|url=https://www.itworld.com/article/2851688/losing-steam-don-t-drop-everything-to-learn-ruby-on-rails.html|title=Losing steam: Don’t drop everything to learn Ruby on Rails}}
47. ^{{cite web|url=https://www.infoworld.com/article/3202651/application-development/rubys-decline-in-popularity-may-be-permanent.html|title=Ruby’s decline in popularity may be permanent}}
48. ^{{cite web|url=https://www.ruby-lang.org/en/news/2017/12/25/ruby-2-5-0-released/|title=Ruby 2.5.0 Released|accessdate=2018-05-02}}
49. ^{{cite web | url = https://www.ruby-lang.org/en/news/2018/12/25/ruby-2-6-0-released/ | title = Ruby 2.6.0 Released | website = Ruby Programming Language | date = 2018-12-25 | accessdate = 2018-12-25}}
50. ^{{cite web|url=http://www.rubyinside.com/the-ruby-communitys-christmas-releases-4118.html/|title=|website=www.rubyinside.com}}
51. ^{{cite web|url=https://blog.heroku.com/archives/2013/12/5/a_patch_in_time_securing_ruby|title=A Patch in Time: Securing Ruby|publisher=}}
52. ^{{cite web|url=https://www.ruby-lang.org/en/news/2003/08/04/ruby-180-released/|title=ruby-1.8.0 released!|website=www.ruby-lang.org}}
53. ^{{cite web|url=https://www.ruby-lang.org/en/news/2011/10/06/plans-for-1-8-7/|title=Plans for 1.8.7|website=www.ruby-lang.org}}
54. ^{{cite web|url=https://www.ruby-lang.org/en/news/2014/07/01/eol-for-1-8-7-and-1-9-2/|title=EOL for Ruby 1.8.7 and 1.9.2|website=www.ruby-lang.org}}
55. ^{{cite web|url=https://www.ruby-lang.org/en/news/2014/11/13/ruby-1-9-3-p551-is-released/|title=Ruby 1.9.3-p551 Released|website=www.ruby-lang.org}}
56. ^{{cite web|url=https://www.ruby-lang.org/en/news/2007/12/25/ruby-1-9-0-released/|title=Ruby 1.9.0 Released|website=www.ruby-lang.org}}
57. ^{{cite web|url=https://www.ruby-lang.org/en/news/2014/01/10/ruby-1-9-3-will-end-on-2015/|title=Support for Ruby version 1.9.3 will end on February 23, 2015|website=www.ruby-lang.org}}
58. ^{{cite web|url=https://www.ruby-lang.org/en/news/2015/02/23/support-for-ruby-1-9-3-has-ended/|title=Support for Ruby 1.9.3 has ended|website=www.ruby-lang.org}}
59. ^¹²{{cite web|url=https://www.ruby-lang.org/en/news/2015/12/16/ruby-2-0-0-p648-released/|title=Ruby 2.0.0-p648 Released|website=www.ruby-lang.org}}
60. ^{{cite web|url=https://www.ruby-lang.org/en/news/2013/02/24/ruby-2-0-0-p0-is-released/|title=Ruby 2.0.0-p0 is released|website=www.ruby-lang.org}}
61. ^{{cite web|url=https://www.ruby-lang.org/en/news/2016/04/01/ruby-2-1-10-released/|title=Ruby 2.1.10 Released|website=www.ruby-lang.org}}
62. ^{{cite web|url=https://www.ruby-lang.org/en/news/2013/12/25/ruby-2-1-0-is-released/|title=Ruby 2.1.0 is released|website=www.ruby-lang.org}}
63. ^{{cite web|url=https://www.ruby-lang.org/en/news/2016/02/24/support-plan-of-ruby-2-0-0-and-2-1/|title=Support plans for Ruby 2.0.0 and Ruby 2.1|website=www.ruby-lang.org}}
64. ^{{cite web|url=https://www.ruby-lang.org/en/news/2016/03/30/ruby-2-1-9-released/|title=Ruby 2.1.9 Released|website=www.ruby-lang.org}}
65. ^{{cite web|url=https://bugs.ruby-lang.org/projects/ruby/wiki/ReleaseEngineering|title=ReleaseEngineering - Ruby - Ruby Issue Tracking System|website=bugs.ruby-lang.org}}
66. ^{{cite web|url=https://www.ruby-lang.org/en/news/2017/04/01/support-of-ruby-2-1-has-ended/|title=Support of Ruby 2.1 has ended|website=www.ruby-lang.org}}
67. ^{{cite web|url=https://www.ruby-lang.org/en/news/2018/03/28/ruby-2-2-10-released/|title=Ruby 2.2.10 Released|website=www.ruby-lang.org}}
68. ^{{cite web|url=https://www.ruby-lang.org/en/news/2014/12/25/ruby-2-2-0-released/|title=Ruby 2.2.0 Released|website=www.ruby-lang.org}}
69. ^{{cite web|url=https://www.ruby-lang.org/en/news/2017/03/28/ruby-2-2-7-released/|title=Ruby 2.2.7 Released|website=www.ruby-lang.org}}
70. ^{{cite web|url=https://www.ruby-lang.org/en/news/2017/04/01/support-of-ruby-2-1-has-ended/|title=Support of Ruby 2.1 has ended|website=www.ruby-lang.org}}
71. ^{{cite web|url=https://www.ruby-lang.org/en/news/2018/10/17/ruby-2-3-8-released/|title=Ruby 2.3.8 Released|website=www.ruby-lang.org}}
72. ^{{cite web|url=https://www.ruby-lang.org/en/news/2015/12/25/ruby-2-3-0-released/|title=Ruby 2.3.0 Released|website=www.ruby-lang.org}}
73. ^¹{{cite web|url=https://www.ruby-lang.org/en/news/2018/06/20/support-of-ruby-2-2-has-ended/|title=Support of Ruby 2.2 has ended|website=www.ruby-lang.org}}
74. ^{{cite web|url=https://www.ruby-lang.org/en/news/2018/10/17/ruby-2-4-5-released/|title=Ruby 2.4.5 Released|last=|first=|date=|website=www.ruby-lang.org|access-date=}}
75. ^{{cite web|url=https://www.ruby-lang.org/en/news/2016/12/25/ruby-2-4-0-released/|title=Ruby 2.4.0 Released|website=www.ruby-lang.org}}
76. ^{{cite web | url = https://www.ruby-lang.org/en/news/2019/03/15/ruby-2-5-5-released/ | title = Ruby 2.5.5 Released | website = Ruby Programming Language | date = 2019-03-15 | accessdate = 2019-03-25}}
77. ^{{cite web|url=https://www.ruby-lang.org/en/news/2017/12/25/ruby-2-5-0-released/|title=Ruby 2.5.0 Released|website=www.ruby-lang.org}}
78. ^{{cite web|url=https://www.ruby-lang.org/en/news/2018/12/25/ruby-2-6-0-released/|title=Ruby 2.6.0 Released|website=www.ruby-lang.org}}
79. ^{{cite web|url=https://blog.heroku.com/ruby-3-by-3|title=Ruby 3x3: Matz, Koichi, and Tenderlove on the future of Ruby Performance|publisher=}}
80. ^{{cite web|url=http://www.mangrove.com/en/journal/2015-11-17-whats-coming-in-ruby-3-and-rails-5/|title=What’s coming in Ruby 3 and Rails 5 - Mangrove|website=www.mangrove.com}}
81. ^{{cite web|url=http://www.informit.com/articles/article.aspx?p=18225|title=The Ruby Programming Language|publisher=|accessdate=2 May 2015}}
82. ^{{YouTube|oEkJvvGEtB4|Google Tech Talks – Ruby 1.9}}
83. ^¹²{{cite web|url=http://www.artima.com/intv/ruby4.html|title=The Philosophy of Ruby|author=Bill Venners|publisher=|accessdate=2 May 2015}}
84. ^{{cite web|url=http://www.rubyweeklynews.org/20050529|title=Welcome to RUBYWEEKLYNEWS.ORG|date=4 July 2017|publisher=|deadurl=bot: unknown|archiveurl=https://web.archive.org/web/20170704073422/http://www.rubyweeklynews.org/20050529|archivedate=4 July 2017|df=}}
85. ^{{cite web|url=https://linuxdevcenter.com/pub/a/linux/2001/11/29/ruby.html|title=An Interview with the Creator of Ruby - O'Reilly Media|author=Bruce Stewart|date=29 November 2001|publisher=|accessdate=2 May 2015}}
86. ^{{cite web|url=http://www.artima.com/intv/tuesday3.html|title=Dynamic Productivity with Ruby|author=Bill Venners|publisher=|accessdate=2 May 2015}}
87. ^{{cite web|url=http://martinfowler.com/articles/languageWorkbench.html|title=Language Workbenches: The Killer-App for Domain Specific Languages?|work=martinfowler.com|accessdate=2 May 2015}}
88. ^{{cite web|url=http://www.codeproject.com/useritems/Ruby_Dynamic_Methods.asp|title=Ruby – Add class methods at runtime|publisher=}}
89. ^{{cite web|url=http://www.artima.com/intv/closures.html|title=Blocks and Closures in Ruby|author=Bill Venners|publisher=|accessdate=2 May 2015}}
90. ^{{cite web | url = https://www.ruby-doc.org/stdlib-2.0.0/ | title = Ruby 2.0.0 Standard Library Documentation | accessdate = 2013-12-09 | last = Britt | first = James}}
91. ^Green threads
92. ^{{cite web|url=http://www.rootr.net/rubyfaq-2.html|title=The Ruby Language FAQ: How Does Ruby Stack Up Against...?|publisher=|accessdate=2 May 2015}}
93. ^{{cite web|title=[ruby-talk:01120] Re: The value of while...|quote=In Ruby's syntax, statement is just a special case of an expression that cannot appear as an argument (e.g. multiple assignment).|url=http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/1120}}
94. ^{{cite web|title=[ruby-talk:02460] Re: Precedence question|quote=statement [...] can not be part of expression unless grouped within parentheses.|url=http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/2460}}
95. ^¹{{cite web|url=https://www.ruby-lang.org/en/news/2013/06/30/we-retire-1-8-7/|title=We retire Ruby 1.8.7|publisher=|accessdate=2 May 2015}}
96. ^{{cite web|url=https://github.com/remore/virtual_module|title=GitHub - remove/virtual_module: Born to make your Ruby Code more than 3x faster. Hopefully.}}
97. ^{{cite web | url = http://www.rubyinside.com/the-why-what-and-how-of-rubinius-1-0-s-release-3261.html | title = The Why, What, and How of Rubinius 1.0's Release | author = Peter Cooper | date = 2010-05-18}}
98. ^{{cite web|url=http://www-4.ibm.com/software/developer/library/ruby.html |title=IBM developerWorks – Ruby: a new language |author=Maya Stodte |date=February 2000 |accessdate=3 March 2014 |deadurl=yes |archiveurl=https://web.archive.org/web/20000818164241/http://www-4.ibm.com/software/developer/library/ruby.html |archivedate=August 18, 2000 }}
99. ^{{cite web|url=http://osdir.com/ml/lang-ruby-general/2002-08/msg02494.html|title=lang-ruby-general: Re: question about Ruby initial development|author=Yukihiro Matsumoto|date=August 2002|accessdate=3 March 2014}}
100. ^{{cite web|url=http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/170|title=ruby-talk: Re: hah, check these errors|author=Yukihiro Matsumoto|date=5 January 1999|accessdate=3 March 2014}}
101. ^{{cite web|url=http://msdn.microsoft.com/en-us/magazine/ff960707.aspx|title=Iron Ruby on Windows Phone 7}}
102. ^{{cite web |url=https://www.ruby-toolbox.com |title=The Ruby Toolbox |accessdate=2015-04-04 }}
103. ^{{cite web|url=https://www.ruby-lang.org/en/news/2013/08/08/rip-raa/|title=We retire raa.ruby-lang.org|date=2013-08-08|accessdate=2016-01-03}}