December 20th, 2012
(written by lawrence krubner, however indented passages are often quotes). You can contact lawrence at: email@example.com
10 years ago, Ruby was still somewhat new to the world, and the programmers who discovered it and promoted were of a very high caliber. But Ruby has gone mainstream now, and it now attracts a large percentage of mediocre programmers. Thus, I am not terribly surprised to read about Ruby programmers who know little about Threads:
I spoke recently at Rubyconf 2011 on some advanced topics in threading. What surprised me was how little experience people had with threads so I decided to write this post to give people a little more background on threads. Matz actually recommends not using threads (see below for why) and I think this is a big reason why Rubyists tend not to understand threading.
Every time you execute ruby, rails or irb, you are creating a process. Within each process, you have something which is executing the code in your process. This is called a thread.
Your operating system starts every process with a “main” thread. Ruby allows you to create as many additional threads as you want by calling Thread.new with a block of code to be executed. Once the block of code has finished executing, the thread is considered dead. If the main thread exits, the process dies.