Yehuda Katz - Why Rails is Hard (Railsberry 2012)
Why Hacker News recommends it
Recommended to people who call Rails bloated, as an argument that its size comes from features you eventually need.
What it is
Yehuda Katz's Railsberry 2012 talk on why Rails is hard to learn and use. He explains that the framework's many features reflect real complexity in web applications that newcomers do not yet see.
Recommended by 2 HN commenters across 2 different months, 2013 to 2014.
What Hacker News said
Recommends gingerlime · 2013-04 · 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 talk[1] by Yehuda Katz: "why rails is hard". One of the key points, if I
Recommends dham · 2014-04 · 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. [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.
Cites cllns · 2013-05 · 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: [this video] )
Cites danneu · 2013-10 · 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