Business is slow for Ruby Private Investigator, Deirdre Bug. She’s on the verge of switching industry when she gets a call from an anxious young man. "Some class methods have gone missing," he tells her breathlessly. "I need your help." Deirdre takes the case and begins exploring Ruby objects behind the scenes. Though she thinks she's on familiar ground — Ruby's object model, method lookup — she's about to discover that she really has no clue.
Nadia co-founded Ignition Works in order to find fun and sustainable ways to build worthwhile software products. She has taught good engineering practices through pair programming at Pivotal Labs and she runs the Ruby Book Club podcast in her spare time.
Oli is a software developer who enjoys working with Ruby and Swift. He’s worked on a range of projects for both startups and giants at Pivotal Labs & thoughtbot, where he cemented an appreciation of testing everything.
To get maximum performance out of a language, compilation is key, and people have been trying to compile Ruby for a long time, ranging from jRuby and Truffle Ruby to the experimental method JIT in Ruby 2.6. But Ruby is a very challenging language to compile efficiently.
The talk will explore some of the reasons based on what Vidar has learned while working on his own Ruby compiler as described in his series of blog posts here.
I've been programming since was a was a kid, and left university to start my first company. Since then I've co-founded a number of tech companies. It was during one of those startups I started using Ruby in 2005. Compiler technology has always been a special interest of mine, and since 2008 I've been semi-regularly working on a Ruby compiler written in Ruby.