3 Reasons Not to Use Ruby
summary
Project digitizes Smithsonian collections with 5 million dried plant specimens and no digital records for 3.7 million of them; the existing tool is PHP on Drupal, which wins because Drupal has far higher active installs and a plug‑in component ecosystem. Prototype UI and parsing get built in Ruby over weeks and then rewrote in PHP in four hours, showing interoperability and deployment speed matter more than language when most work is integration, not new code.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:11SKYLIGHT
- 6:55Software Evolution
- 9:41High Level Components
- 12:33Language Choice
- 14:32Patterns for How we work
related talks
45mRuby Prototyping for Impact
36mData Management with Ruby
40mReinvesting in Ruby
34mBuilding Data Driven Products with Ruby
24mCreativity with Ruby-Processing
40mRunning a Government Department on Ruby for over 13 Years
37mExtreme Makeover: Rubygems Edition
36mWhat's Wrong With Ruby's Object Model (And Why That's a Good Thing)