Yehuda Katz - Why Rails is Hard (Railsberry 2012)
Channel:applicake · Length:53:11 · Published:2012-05-28 · Views:29461
Summary
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.
Why HN recommends it
Recommended to people who call Rails bloated, as an argument that its size comes from features you eventually need.
I've seen an interesting talk[1] by Yehuda Katz: "why rails is hard". — HN, 2013
Python, Ruby & scripting languages · Web development · Software architecture & design
Subtitles (excerpt)
[Music] and now officially hey welcome to the second day of girl um pretty impressive that so many of you are here I'm happy that I have some of my voice left and it's my team is very uh is making fun of me that is actually Poss possible for me to talk too much so this is probably what's happening uh I'm very happy to welcome uh Yehuda uh today and I'll just leave uh the stage with him so give him a big [Applause] [Applause] hands okay so Hey so uh thank you everybody for being here so early in the morning it's at least hard for me I don't know about everybody else um so my talk today is uh called why rails is hard and uh the motivation behind this talk is that there's a I feel there's a trend in open source today and I think it's largely driven by the emergence of JavaScript uh entering our ecosystem I'm I'm very so I think uh there's a an emerging uh mentality that the only kind of good software is small and simple software and if you're software is doing too many things it's de facto automatically by definition bad wrong uh you're doing it wrong you should be writing small decoupled software that does one thing and does one thing right uh is I think the nice version of it but really it's it's just a a backlash against software that does more than a little
On Hacker News
Rails is not bloated, it just comes with a lot of features. I'd suggest watching these videos. [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 R… — dham, 2014-04
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 ro… — gingerlime, 2013-04
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 … — danneu, 2013-10
(Un)conscious (in)competence reminds me of Donald Rumsfeld's trichotomy of known knowns, known unknowns and unknown unknowns. (highlighted here: [VIDEO] ) — cllns, 2013-05
Related videos
- Stop Writing Classes · Next Day Video · 27:29
- Ruby Conf 12 - Y Not- Adventures in Functional Programming by Jim Weirich · Confreaks · 53:21
- The spelled-out intro to neural networks and backpropagation: building micrograd · Andrej Karpathy · 2:25:52
- How Python was Shaped by leaky Internals, Armin Ronacher, Flask framework · Видео с мероприятий {speach! · 49:55
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- "Simple Made Easy" - Rich Hickey (2011) · Strange Loop Conference · 1:01:38
- What the heck is the event loop anyway? | Philip Roberts | JSConf EU · JSConf · 26:52
- Rich Harris - Rethinking reactivity · You Gotta Love Frontend · 36:45
- "Making Impossible States Impossible" by Richard Feldman · elm-conf · 25:06
- How To Design A Good API and Why it Matters · Google TechTalks · 1:00:19
- The Problem with Time & Timezones - Computerphile · Computerphile · 10:12
- The Value of Values with Rich Hickey · InfoQ · 31:43
- Overwatch Gameplay Architecture and Netcode · GDC Festival of Gaming · 1:04:03
- Solving Problems the Clojure Way - Rafal Dittwald · Clojure/north · 1:02:26
- Lecture 1A: Overview and Introduction to Lisp · MIT OpenCourseWare · 1:12:55
- Alan Kay - Normal Considered Harmful · powerfuloutlet · 1:07:26