Coding for Finance



Tab nameTab nameTab name
Tab content
Tab content
Tab content

Ruby is an interpreted, high-level, general-purpose programming language. It was designed with an emphasis on programming productivity and simplicity. In Ruby, everything is an object, including primitive data types. It was developed in the mid-1990s by Yukihiro "Matz" Matsumoto in Japan.

Ruby is dynamically typed and uses garbage collection and just-in-time compilation. It supports multiple programming paradigms, including procedural, object-oriented, and functional programming. According to the creator, Ruby was influenced by Perl, Smalltalk, Eiffel, Ada, BASIC, Java, and Lisp.[10][3]


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:

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.[11] He praised the language for its ingenuity and creativity for its solution for compiling intervals.

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

Early releases

The first public release of Ruby 0.95 was announced on Japanese domestic newsgroups on December 21, 1995.[16][17] Subsequently, three more versions of Ruby were released in two days.[12] 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.[18]

After the release of Ruby 0.95 in 1995, several stable versions of Ruby were released in these years:

  • Ruby 1.0: December 25, 1996[12]
  • Ruby 1.2: December 1998
  • Ruby 1.4: August 1999
  • Ruby 1.6: September 2000

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

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

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

By 2000, Ruby was more popular than Python in Japan.[20] 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 and 1.9

Ruby 1.8 was initially released August 2003, was stable for a long time, and was retired June 2013.[21] 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[22] and an international standard (ISO/IEC 30170) in 2012.[23][24]

Ruby on Rails logo

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.[25]

Effective with Ruby 1.9.3, released October 31, 2011,[26] 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.[27] 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. Examples include:[28]

  • block local variables (variables that are local to the block in which they are declared)
  • an additional lambda syntax: f = ->(a,b) { puts a + b }
  • an additional Hash literal syntax using colons for symbol keys: {symbol_key: "value"} == {:symbol_key => "value"}
  • per-string character encodings are supported
  • new socket API [IPv6 support]
  • require_relative import security

Ruby 2

Ruby 2.0 was 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.[29] Ruby 2.0 added several new features, including:

  • Method keyword arguments
  • A new method, Module#prepend, to extend a class
  • A new literal to create an array of symbols
  • New API for lazy evaluation of Enumerables
  • A new convention of using #to_h to convert objects to Hashes[30]

Starting with 2.1.0, Ruby's versioning policy changed to be more similar to semantic versioning.[31]

Ruby 2.2.0 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. Since version 2.2.1,[32] Ruby MRI performance on PowerPC64 was improved.[33][34][35] 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.[36]

Ruby 2.3.0 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.[37] Other notable changes include:

  • The ability to mark all string literals as frozen by default with a consequently large performance increase in string operations.[38]
  • 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 if obj && &&, 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.

Ruby 2.4.0 includes performance improvements to hash table, Array#max, Array#min, and instance variable access.[39] Other 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

A few notable changes in Ruby 2.5.0 include rescue and ensure statements automatically use a surrounding do-end block (less need for extra begin-end blocks), method-chaining with yield_self, support for branch coverage and method coverage measurement, and easier Hash transformations with Hash#slice and Hash#transform_keys 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.

A few notable changes in Ruby 2.6.0 include an experimental just-in-time compiler (JIT), and RubyVM::AbstractSyntaxTree (experimental).

A few notable changes in Ruby 2.7.0 include pattern Matching (experimental), REPL improvements, a compaction GC, and separation of positional and keyword arguments.

Ruby 3

Ruby 3.0.0 was released on Christmas Day in 2020.[40] It is known as Ruby 3x3 which means that programs would run three times faster in Ruby 3.0 comparing to Ruby 2.0.[41] and some had already implemented in intermediate releases on the road from 2 to 3. To achieve 3x3, Ruby 3 comes with MJIT, and later YJIT, Just-In-Time Compilers, to make programs faster, although they are described as experimental and remain disabled by default (enabled by flags at runtime).

Another goal of Ruby 3.0 is to improve concurrency and two more utilities Fibre Scheduler, and experimental Ractor facilitate the goal.[40] Ractor is light-weight and thread-safe as it is achieved by exchanging messages rather than shared objects.

Ruby 3.0 introduces RBS language to describe the types of Ruby programs for static analysis.[40] It is separated from general Ruby programs.

There are some syntax enhancements and library changes in Ruby 3.0 as well.[40]

Ruby 3.1 was released on December 25, 2021.[42] It includes YJIT, a new, experimental, Just-In-Time Compiler developed by Shopify, to enhance the performance of real world business applications. A new debugger is also included. There are some syntax enhancements and other improvements in this release. Network libraries for FTP, SMTP, IMAP, and POP are moved from default gems to bundled gems.[43]

Ruby 3.2 was released on December 25, 2022.[44] It brings support for being run inside of a WebAssembly environment via a WASI interface. Regular expressions also receives some improvements, including a faster, memoized matching algorithm to protect against certain ReDoS attacks, and configurable timeouts for regular expression matching. Additional debugging and syntax features are also included in this release, which include syntax suggestion, as well as error highlighting. The MJIT compiler has been re-implemented as a standard library module, while the YJIT, a Rust-based JIT compiler now supports more architectures on Linux.

Ruby 3.3 was released on December 25, 2023.[1] Ruby 3.3 introduces significant enhancements and performance improvements to the language. Key features include the introduction of the Prism parser for portable and maintainable parsing, the addition of the pure-Ruby JIT compiler RJIT, and major performance boosts in the YJIT compiler. Additionally, improvements in memory usage, the introduction of an M:N thread scheduler, and updates to the standard library contribute to a more efficient and developer-friendly Ruby ecosystem.

Semantics and philosophy

Yukihiro Matsumoto, the creator of Ruby

Matsumoto has said that Ruby is designed for programmer productivity and fun, following the principles of good user interface design.[45] At a Google Tech Talk in 2008 he said, "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."[46] He stresses that systems design needs to emphasize human, rather than computer, needs:[47]

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.

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 (POLA) to the design of Ruby;[47] 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.[48]

Matsumoto defined it this way in an interview:[47]

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.

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"). Because everything in Ruby is an object, everything in Ruby has certain built-in abilities called methods. 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, reflective programming, metaprogramming, and interpreter-based threads. Ruby features dynamic typing, and supports parametric polymorphism.

According to the Ruby FAQ, the syntax is similar to Perl's and the semantics are similar to Smalltalk's, but the design philosophy differs greatly from Python's.[49]



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 defined by either 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.[57][58] 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 trade-off 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.


Matz's Ruby interpreter

The original Ruby interpreter is often referred to as 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.[21]

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.

Alternative implementations

As of 2018, there are a number of alternative implementations of Ruby, including JRuby, Rubinius, and mruby. Each takes a different approach, with JRuby and Rubinius providing just-in-time compilation and mruby also providing ahead-of-time compilation.

Ruby has three major alternative implementations:

  • JRuby, a mixed Java and Ruby implementation that runs on the Java virtual machine. JRuby currently targets Ruby 3.1.x.
  • 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.3.1.

Other Ruby implementations include:

Other now defunct Ruby implementations were:

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, JRuby, and Rubinius[60] are all able to run Rails unmodified in a production environment.

Platform support

Matsumoto originally developed Ruby on the 4.3BSD-based Sony NEWS-OS 3.x, but later migrated his work to SunOS 4.x, and finally to Linux.[61][62] By 1999, Ruby was known to work across many different operating systems. Modern Ruby versions and implementations are available on all major desktop, mobile and server-based operating systems. Ruby is also supported across a number of cloud hosting platforms like Jelastic, Heroku, Google Cloud Platform and others.

Tools such as RVM and RBEnv, facilitate installation and partitioning of multiple ruby versions, and multiple 'gemsets' on one machine.

Repositories and libraries

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

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.[65]

See also


  1. ^ a b "Ruby 3.3.0 Released". Archived from the original on 2023-12-25. Retrieved 2023-12-25.
  2. ^ a b c Cooper, Peter (2009). Beginning Ruby: From Novice to Professional. Beginning from Novice to Professional (2nd ed.). Berkeley: APress. p. 101. ISBN 978-1-4302-2363-4. To a lesser extent, Python, LISP, Eiffel, Ada, and C++ have also influenced Ruby.
  3. ^ a b "Reasons behind Ruby". Ruby Conference 2008. Confreaks TV. Archived from the original on 2020-01-15. Retrieved 2019-06-25.
  4. ^ a b c d e f Bini, Ola (2007). Practical JRuby on Rails Web 2.0 Projects: Bringing Ruby on Rails to Java. Berkeley: APress. p. 3. ISBN 978-1-59059-881-8. It draws primarily on features from Perl, Smalltalk, Python, Lisp, Dylan, and CLU.
  5. ^ "Julia 1.0 Documentation: Introduction". Archived from the original on 16 August 2018. Retrieved 6 October 2018.
  6. ^ Burks, Tim. "About Nu™". Programming Nu™. Neon Design Technology, Inc. Archived from the original on 2018-12-25. Retrieved 2011-07-21.
  7. ^ Ring Team (3 December 2017). "Ring and other languages". ring-lang. Archived from the original on 25 December 2018. Retrieved 3 December 2017.
  8. ^ "Influences - The Rust Reference". The Rust Reference. Archived from the original on 2019-01-26. Retrieved 2023-04-18.
  9. ^ Lattner, Chris (2014-06-03). "Chris Lattner's Homepage". Chris Lattner. Archived from the original on 2018-12-25. Retrieved 2014-06-03. 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.
  10. ^ "About Ruby". Archived from the original on 9 October 2014. Retrieved 15 February 2020.
  11. ^ Matsumoto, Yukihiro (13 February 2006). "Re: Ruby's lisp features". Archived from the original on 2018-10-27. Retrieved 15 February 2020.
  12. ^ a b c d e f "History of Ruby". Archived from the original on 2011-07-14. Retrieved 2008-08-14.
  13. ^ "[FYI: historic] The decisive moment of the language name Ruby. (Re: [ANN] ruby 1.8.1)" (E-mail from Hiroshi Sugihara to ruby-talk). Archived from the original on 2011-07-17. Retrieved 2008-08-14.
  14. ^ "1.3 Why the name 'Ruby'?". The Ruby Language FAQ. Archived from the original on May 28, 2012. Retrieved April 10, 2012.
  15. ^ Yukihiro Matsumoto (June 11, 1999). "Re: the name of Ruby?". Ruby-Talk (Mailing list). Archived from the original on December 25, 2018. Retrieved April 10, 2012.
  16. ^ "More archeolinguistics: unearthing proto-Ruby". Archived from the original on 6 November 2015. Retrieved 2 May 2015.
  17. ^ "[ruby-talk:00382] Re: history of ruby". Archived from the original on 16 July 2011. Retrieved 2 May 2015.
  18. ^ "[ruby-list:124] TUTORIAL — ruby's features". Archived from the original on 24 May 2003. Retrieved 2 May 2015.
  19. ^ "An Interview with the Creator of Ruby". Archived from the original on 2008-02-08. Retrieved 2007-07-11.
  20. ^ Yukihiro Matsumoto (October 2000). "Programming Ruby: Forward". Archived from the original on 25 December 2018. Retrieved 5 March 2014.
  21. ^ a b "We retire Ruby 1.8.7". Archived from the original on 6 June 2015. Retrieved 2 May 2015.
  22. ^ "IPA 独立行政法人 情報処理推進機構:プレス発表 プログラム言語RubyのJIS規格(JIS X 3017)制定について". Archived from the original on 2 February 2015. Retrieved 2 May 2015.
  23. ^ "IPA 独立行政法人 情報処理推進機構:プレス発表 プログラム言語Ruby、国際規格として承認". Archived from the original on 1 February 2015. Retrieved 2 May 2015.
  24. ^ "ISO/IEC 30170:2012". Archived from the original on 2017-03-12. Retrieved 2017-03-10.
  25. ^ Web Development: Ruby on Rails Archived 2009-02-24 at the Wayback Machine. (2007-03-22). Retrieved on 2013-07-17.
  26. ^ "Ruby 1.9.3 p0 is released". October 31, 2011. Archived from the original on January 14, 2013. Retrieved February 20, 2013.
  27. ^ "v1_9_3_0/NEWS". Ruby Subversion source repository. September 17, 2011. Archived from the original on November 6, 2015. Retrieved February 20, 2013.
  28. ^ Ruby 1.9: What to Expect Archived 2016-03-04 at the Wayback Machine. Retrieved on 2013-07-17.
  29. ^ Endoh, Yusuke. (2013-02-24) Ruby 2.0.0-p0 is released Archived 2013-02-27 at the Wayback Machine. Retrieved on 2013-07-17.
  30. ^ Endoh, Yusuke. (2013-02-24) Ruby 2.0.0-p0 is released Archived 2016-01-17 at the Wayback Machine. Retrieved on 2013-07-17.
  31. ^ "Semantic Versioning starting with Ruby 2.1.0". December 21, 2013. Archived from the original on February 13, 2014. Retrieved December 27, 2013.
  32. ^ Gustavo Frederico Temple Pedrosa, Vitor de Lima, Leonardo Bianconi (2015). "Ruby 2.2.1 Released". Archived from the original on 16 May 2016. Retrieved 12 July 2016.{{cite web}}: CS1 maint: multiple names: authors list (link)
  33. ^ Gustavo Frederico Temple Pedrosa, Vitor de Lima, Leonardo Bianconi (2015). "v2.2.1 ChangeLog". Archived from the original on 26 February 2017. Retrieved 12 July 2016.{{cite web}}: CS1 maint: multiple names: authors list (link)
  34. ^ Gustavo Frederico Temple Pedrosa, Vitor de Lima, Leonardo Bianconi (2014). "Specifying non volatile registers for increase performance in ppc64". Archived from the original on 17 September 2016. Retrieved 12 July 2016.{{cite web}}: CS1 maint: multiple names: authors list (link)
  35. ^ Gustavo Frederico Temple Pedrosa, Vitor de Lima, Leonardo Bianconi (2014). "Specifying MACRO for increase performance in ppc64". Archived from the original on 17 September 2016. Retrieved 12 July 2016.{{cite web}}: CS1 maint: multiple names: authors list (link)
  36. ^ "ruby/NEWS at v2_2_0 · ruby/ruby · GitHub". GitHub. Archived from the original on 1 January 2015. Retrieved 2 May 2015.
  37. ^ "Ruby/NEWS at v.2_3_0 - ruby/ruby". GitHub. Archived from the original on 1 March 2017. Retrieved 25 December 2015.
  38. ^ "Ruby 2.3.0 changes and features". Running with Ruby. 14 November 2015. Archived from the original on 5 January 2016. Retrieved 27 December 2015.
  39. ^ "Ruby 2.4.0 Released". Archived from the original on 2017-02-17. Retrieved 2016-12-30.
  40. ^ a b c d "Ruby 3.0.0 Released". Ruby Programming Language. 2020-12-25. Archived from the original on 2020-12-25. Retrieved 2020-12-25.
  41. ^ Scheffler, Jonan (November 10, 2016). "Ruby 3x3: Matz, Koichi, and Tenderlove on the future of Ruby Performance". Ruby. Archived from the original on May 10, 2019. Retrieved May 18, 2019.
  42. ^ "Ruby 3.1.0 Released". Archived from the original on 25 December 2021. Retrieved 25 Dec 2021.
  43. ^ "Ruby 3.1.0 Released". Archived from the original on 2021-12-26. Retrieved 2021-12-26.
  44. ^ "Ruby 3.2.0 Released". Archived from the original on 2022-12-25. Retrieved 2022-12-25.
  45. ^ "The Ruby Programming Language". Archived from the original on 18 January 2020. Retrieved 2 May 2015.
  46. ^ Google Tech Talks – Ruby 1.9 on YouTube
  47. ^ a b c Bill Venners. "The Philosophy of Ruby". Archived from the original on 5 July 2019. Retrieved 2 May 2015.
  48. ^ "Welcome to RUBYWEEKLYNEWS.ORG". 4 July 2017. Archived from the original on 4 July 2017.{{cite web}}: CS1 maint: bot: original URL status unknown (link)
  49. ^ "The Ruby Language FAQ: How Does Ruby Stack Up Against...?". Archived from the original on 8 May 2015. Retrieved 2 May 2015.
  50. ^ Bruce Stewart (29 November 2001). "An Interview with the Creator of Ruby". O'Reilly Media. Archived from the original on 6 May 2015. Retrieved 2 May 2015.
  51. ^ Bill Venners. "Dynamic Productivity with Ruby". Archived from the original on 5 September 2015. Retrieved 2 May 2015.
  52. ^ "Language Workbenches: The Killer-App for Domain Specific Languages?". Archived from the original on 2 May 2021. Retrieved 2 May 2015.
  53. ^ "Ruby – Add class methods at runtime". Archived from the original on 2007-09-22. Retrieved 2007-11-01.
  54. ^ Bill Venners. "Blocks and Closures in Ruby". Archived from the original on 18 April 2015. Retrieved 2 May 2015.
  55. ^ "Methods". Official Ruby FAQ. Archived from the original on 2022-06-28. Retrieved 2021-06-20.
  56. ^ Britt, James. "Ruby 2.0.0 Standard Library Documentation". Archived from the original on 2013-11-13. Retrieved 2013-12-09.
  57. ^ "[ruby-talk:01120] Re: The value of while..." Archived from the original on 2011-07-17. Retrieved 2008-12-06. In Ruby's syntax, statement is just a special case of an expression that cannot appear as an argument (e.g. multiple assignment).
  58. ^ "[ruby-talk:02460] Re: Precedence question". Archived from the original on 2004-07-22. Retrieved 2008-12-06. statement [...] can not be part of expression unless grouped within parentheses.
  59. ^ "remove/virtual_module: Born to make your Ruby Code more than 3x faster. Hopefully". GitHub. 21 February 2020. Archived from the original on 1 March 2017. Retrieved 29 August 2016.
  60. ^ Peter Cooper (2010-05-18). "The Why, What, and How of Rubinius 1.0's Release". Archived from the original on 2010-05-24. Retrieved 2010-05-23.
  61. ^ Maya Stodte (February 2000). "IBM developerWorks – Ruby: a new language". Archived from the original on August 18, 2000. Retrieved 3 March 2014.
  62. ^ Yukihiro Matsumoto (August 2002). "lang-ruby-general: Re: question about Ruby initial development". Archived from the original on 3 March 2014. Retrieved 3 March 2014.
  63. ^ "The Ruby Toolbox". Archived from the original on 2015-04-03. Retrieved 2015-04-04.
  64. ^ "Stats your community gem host". Archived from the original on 10 December 2021. Retrieved 10 December 2021.
  65. ^ "We retire". 2013-08-08. Archived from the original on 2015-12-31. Retrieved 2016-01-03.

Further reading

External links

Comments are closed.