Microtalk: Nokogiri - History and Future
summary
Nokogiri claims nearly 10 million downloads and traces a concrete arc: a C extension first, a painful FFI phase (3,000 lines of Ruby vs ~4,000 lines of C, lots of segfault-driven debugging), then a working Java port for JRuby. Debugging uses valgrind and perftools; packaging uses mini_portile and rake-compiler. The practical outcomes are measurable: performance tradeoffs documented, JRuby compatibility achieved, and installer pain reduced by packaging libxml2 into the gem so installations stop failing.
AI-written summary · about
chapters (4)
- 0:00Start
- 0:46PIVOTAL LABS
- 5:13Community acceptance
- 7:00What's FFI? Foreign Function Interface Ruby caling native C code directly
related talks
47mJRuby: What, Why, How... Try It Now
39mJRuby: Insights from Six Years in Production
42mJRuby at 15 Years: Meeting the Challenges
53m20 Years of JRuby - Where We've Been and Where We're Going
29mRuby & JVM: A (JRuby) Love Story
29mFifty Years of Ruby
25mWhy I like JRuby (and you should too)
37mState of JRuby 2014