Ruby Conference 2008 - What All Rubyists Should Know About Threads

[@juanitofatas]

RIP Jim. Thank you for the talk.

[@dfence1985]

RIP Jim, one of the most inspiring rubyists

[@ifeanyiopara3873]

What an interesting talk, RIP Jim

[@angelolakra9192]

RIP Jim

[@dietrichdietrich7763]

This so good. R.I.P. Jim, really motivating.

[@ahmadhasanKhan]

R.I.P Jim

[@dogafincan]

He was such a good teacher

[@enogrob]

...this talk...maybe have inspired the creation of the Elixir language...

[@anikettiwari6885]

Can someone share the source code

[@sreekumarmenon]

what was the Texas joke?

[@maruccioperuccio]

taxes

[@DavidDouglasJr]

what a nut, who uses classes as variables?

[@dietrichdietrich7763]

You're thinking of this like C, Ruby is different. Everything is an Object! Classes as variables is the way to go as a Ruby programmer. Because that way it can be constantly manipulated. Makes sense now?

[@dietrichdietrich7763]

You see, In the C language. You use classes to reiterate different spectrum points - it puts variables to work in different loop processes. Ruby is different, though it shares aspects but it is meant to be more dynamic without going to the low end of manipulating hardware. Hence the multi-threading is different over-all.

[@miry_sof]

It is not classes, but Constants. "A constant has a name starting with an uppercase character. It should be assigned a value at most once."

[@caiovinicius8448]

RIP Jim. Thank you for the talk.