"Ruby native extensions and what's wrong with them"

on YouTube ↗15m

" summary

A scanner that crawls GitHub and downloaded gem packages extracts extconf.rb files, parses the ad hoc C bindings, and builds a gem→library cache showing which gems require which native libraries. The analysis finds thousands of gems with nonstandard extension scripts that defeat simple regex parsing, and many gems silently depend on system dev packages (libssl-dev, libpq-dev, etc.). A working prototype maps gems to required libraries but still needs translation from libraries to OS packages for Ubuntu, CentOS and Alpine.

AI-written summary · about

" chapters (6)

1. 0:00Introduction and motivation
2. 1:03Challenges with Ruby gems
3. 2:41Automating dependency management
4. 4:45Native extensions analysis
5. 7:10Standardization limitations
6. 10:42Developing a mapping tool

" related talks

• 30mBuilding Native Extensions. This Could Take A While...Mike Dalessio · RubyConf 2021
• 24mThe State of C Extensions: Alive and Well, so Learn to DealSam Rawlins · MountainWest RubyConf 2011
• 29mRuby-red onions: Peeling Back Ruby's Layers in C ExtensionsEmily Stolfo · RubyConf 2014
• 38mLong journey of Ruby standard libraryHiroshi Shibata · RubyConf AU 2024
• 35mRuby’s C Extension Problem and How We're Solving ItChris Seaton · RubyConf 2016
• 31mHacking with GemsBen Smith · Aloha RubyConf 2012
• 42mExtending Gems - Patterns and Anti-Patterns of Pluggable GemsJason R. Clark · Open Source Bridge 2014
• 06m⚡️ You Might Not Need GemsAlyssa Ross · Bath Ruby 2018