What I Learned to Love About Ruby When I Switched to Python
summary
Compares concrete tradeoffs: Ruby’s principle of least surprise (methods with ? and !, synonyms like collect/map) versus Python’s strict whitespace errors; version timelines (Ruby 2.0 → 2013, 2.2 → 2014; Python 3 → 2008, Python 2.7 EOL 2020) and upgrade pain; tooling (rvm/rbenv + Bundler/Gemfile and Gemfile.lock versus virtualenv, Anaconda, pip and sparse requirements.txt); tutorials built and what they show (Rails blog with DB logs vs Django creating a superuser/admin); actual bugs found — a query repeated 8–10× causing 10× slower pages. Gemfile.lock transparency
AI-written summary · about
chapters (14)
- 0:00Start
- 1:09Languages
- 2:35The Principle of Least Surprise
- 3:27Principle of Least Surprise
- 5:08Synonyms
- 5:30Documentation
- 6:41Timeline of Ruby and Python
- 9:31Ruby Version Manager
- 10:56Anaconda
- 13:46Version Management
- 16:58Default Configurations
- 17:37Why Do We Set the Log Level in Production
- 18:20Django
- 25:58The Zen of Python
related talks
29mBang the gong, the game is on: What can Python people learn from Ruby?
35mPython for Ruby Programmers
34mThe Modern Rubyist: When and How to Use the Latest Features
31mWhat Ruby Developers Can Learn From Go
35mPython for Ruby Programmers
33mRuby: A Family History
41mTen Things I Hate About Ruby
45mMy favorite things