Skip to content
Hallway
0:00 / 0:00

#rubyonrails#yehudakatz#frameworkdesign

Yehuda Katz - Why Rails is Hard (Railsberry 2012)

applicake

847 subscribers • 2 videos on Hallway

YouTube
  • Recommended by 2 people: 2 on Hacker News.
  • Presented by Yehuda Katz, Rails Core Team member
  • May be out of date. Uploaded 14 years ago, in an area where tools change fast.
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

29K views14 years ago2 recommendations

Web developmentSoftware designRubyFull-stack frameworksSoftware architecture

Yehuda Katz discusses the inherent complexity of web applications and explains why Rails uses high-level abstractions to manage it.

European Rails Conference Railsberry 2012, Day 2

Why it's here

2 people recommend this

What people say. Engineers point to this talk to explain the trade-offs of high-level framework abstractions and the nature of software complexity.

gingerlimeon Hacker News • Recommends

On “Hacking Flask: A Success Story”

I would gladly take Flask over Django/TastyPie Could you explain the benefits or difference for you? Personally, I enjoyed using Tastypie, and when things weren't clear, its code was a pleasure to read and made things easier to understand or work out how to solve. Perhaps similar to your experience with the Flask code. I imagine a thinner framework is cleaner in many ways, but then with a more robust framework you get stuff out of the box. In this particular case, getting the request time (+ if you want, sql time etc) is relatively easy and there are a few middleware options to do it in Django. I've seen an interesting talk1 by Yehuda Katz: "why rails is hard". One of the key points, if I…
View on Hacker News

dhamon Hacker News • Recommends

On “Ask HN: why most startups use ruby and rails?”

Rails is not bloated, it just comes with a lot of features. I'd suggest watching these videos. link to this video link A typical Rails instance will use 100 - 150mb, and does not take a minute to start up. Have you actually used Rails? I have several large projects and none have ever taken that long to startup. I use Ruby for non Rails projects all the time and had no issue finding how to include Active Record and Action Mailer into a Ruby CLI application.
View on Hacker News

cllnson Hacker News • Mentions

On “You are dangerously bad at cryptography”

(Un)conscious (in)competence reminds me of Donald Rumsfeld's trichotomy of known knowns, known unknowns and unknown unknowns. (highlighted here: link to this video )
View on Hacker News

danneuon Hacker News • Mentions

On “Lisp Web Tales”

The difference is that Rails and the popular gems involve some of the highest abstractions I've ever used. It's like that by design. There's nothing inherently bad about it. Here's the typical workflow for adding a gem: 1. Add "gem 'some_library'" to Gemfile 2. `bundle install` 3. Drop the 'some_library_method!' incantation where you need to. Here are the steps for Devise's base-case (I only use Devise as an example for a broader point): 1. echo 'gem "devise"' >> Gemfile 2. `rails generate devise:install` 3. `rails generate devise User` 4. `rails generate devise:views` Boom. It's awesome. The trade-off is that now your entire authentication system is hidden behind line 37 of your Gemfile. An…
View on Hacker News