I'm going to have to insist that you provide more details. This is a technical journal, after all. What did you learn about timing and algorithms? Did Avdi Grim have anything interesting to say about threading in his videos?
He talked about some internal behavior of Ruby threads and the Ruby interpreter, and what this means to a programmer. He talked about how it was important to set the thread_abort_on_exception property, which prevents errors in threads from producing no output. He said that you never want a situation where a portion of your program fails silently. He also talks about ruby's deadlock detection. If all threads are paused, ruby infers that there is a deadlock and stops the program. However, he then gave an example of a deadlocked program with other, unrelated threads running, which would result in a silent deadlock.
I'm going to have to insist that you provide more details. This is a technical journal, after all. What did you learn about timing and algorithms? Did Avdi Grim have anything interesting to say about threading in his videos?
ReplyDeleteHe talked about some internal behavior of Ruby threads and the Ruby interpreter, and what this means to a programmer. He talked about how it was important to set the thread_abort_on_exception property, which prevents errors in threads from producing no output. He said that you never want a situation where a portion of your program fails silently. He also talks about ruby's deadlock detection. If all threads are paused, ruby infers that there is a deadlock and stops the program. However, he then gave an example of a deadlocked program with other, unrelated threads running, which would result in a silent deadlock.
Delete