Sure, they're not looking for headlines, but I wouldn't call it "honest". A chart with a linear scale that shows the full range from 0 to max (no baseline that makes small differences look huge) would be far more honest in my opinion.
The post is old, but still somewhat true. The most important change is how memory carriers can be moved between schedulers/cores nowadays which improves the TLB miss rate and makes for better system locality.
Hello, post author here. What I mean by "N/A" here is "Not Applicable" as in Ruby was not designed for concurrency. I didn't mean to say that it is "Not Available" or not possible. I also was only describing language features without considering libraries.
I'm pretty sure Matz is still working at re-architecting the Ruby global interpreter lock (GIL) for genuine concurrency. JRuby and Rubinius are alternative Implementations of ruby that do support Concurrency, but they are just that, alternative Implementations.
I got that it is building a binary and basically placing it in a local repo. I also get that it is looking for a binary from a GitHub Release first, which is mildly better.
I still think solutions like this are putting your build process at great risk. You will have build issues that are no fault of your own and completely out of your control. Unless you clone the github repository and then use that as your source. And cloning will have issues and risks of its own.