News for hackers. Stuff that matters.

A comment on Ruby Concurrency Final Report. Parent comment

Re:Ruby Concurrency Final Report by giu on Friday April 17, 2020 @08:48AM (#22898505)
In the linked article, the author also included some videos of himself implementing some of the presented parts e.g. exclusive Fibers [0], including writing the necessary C code using the Ruby C API.

Recording yourself writing code and then publishing it takes quite a lot of courage, even moreso if it's a complex topic such as the one presented. Additionally, it's such a valuable resource: You can follow the whole implementation step by step.

That's just awesome.

[0] https://www.youtube.com/watch?v=cNaqbeagqUw

[ Parent | on HN ]
Re:Ruby Concurrency Final Report by psychoslave on Friday April 17, 2020 @11:46PM (#22905162)
That's even super awesome. I didn't watch the whole thing yet, but he seems to comment extensively, as opposed to staying quiet on the inner thoughts during the whole thought process – which is of course the most crucial part.

Thanks for sharing.

[ Parent | on HN ]
Re:Ruby Concurrency Final Report by djohnston on Friday April 17, 2020 @12:43PM (#22900548)
This is really cool. Do you have any recs for similar vid of someone hacking on c python API? I want to gain a better understanding of how these langs interface w their implementation, but Ruby isn't really in my wheelhouse.
[ Parent | on HN ]
Re:Ruby Concurrency Final Report by ioquatix on Friday April 17, 2020 @07:39PM (#22904031)
The internals aren't THAT different, so while I can't really answer your question (I'm not working on CPython), you might still find it interesting from the POV as to how interpreters work.
[ Parent | on HN ]
Re:Ruby Concurrency Final Report by tylerscott on Friday April 17, 2020 @09:02AM (#22898588)
Thanks for the link. This is great!
[ Parent | on HN ]