Ruby's require, autoload and load methods

Autoload is a nice feature, but it's good to know the difference when you begin using multiple files in your projects.

Transcript

1. require autoload load @donschado | 15.01.2014
2. http://ruby-doc.org/core-2.1.0/Kernel.html#method-i-require
5. http://ruby-doc.org/core-2.1.0/Kernel.html#method-i-autoload
7. http://ruby-doc.org/core-2.1.0/Kernel.html#method-i-auto
10. Matz (2011) "discourage the use of autoload" [...] autoload itself has fundamental flaw under multi-thread environment. I should have remove autoload when I added threads to the language. ! [...] I hereby declare the future deprecation of autoload. Ruby will keep autoload for a while, since 2.0 should keep compatibility to 1.9.
 But you don't expect it will survive further future, e.g. 3.0. I strongly discourage the use of autoload in any standard libraries. ” https://bugs.ruby-lang.org/issues/5653 https://www.ruby-forum.com/topic/3036681
11. ”Peter Cooper: I'll be taking the "cross that bridge when I get to it" approach What I think after some research... http://www.rubyinside.com/ruby-techniques-revealed-autoload-1652.html I‘m full of autoload 
 because the lazy loading feature is awesome...