This doc and the Elixir doc don't really capture much imo. They are short and hardly get the origin stories told before ending. There isn't much to get excited about before they are over, and they feel kinda like they exist to stroke the egos of those appearing in the film, and not so much to show the community or more importantly the people outside of the community, how awesome these things are. Give me a 1.5 hour long doc on elixir and rails and get past the patting each other on the backs part and into the struggles over the years, switch back and forth between different uses at different shops, etc. Essentially, steal the format of Indie Game The Movie and I'll be more into these because I want there to be great docs about software
Ruby on Rails: The Documentary [video]
231–240 of 248 posts
Re: Ruby on Rails: The Documentary [video]
#232Two figures that inspired me were missing, why the lucky stiff and Ryan Bates from railcasts fame. Otherwise great docu with DHH "f*uk you" slide which does give an insight into successful open source projects.
I was also expecting Gregg Pollack and Code School to be mentioned.
The "Rails for Zombies" course was absolutely fantastic.
Re: Ruby on Rails: The Documentary [video]
#233Earlier quoted context omitted.
The culture encourages a lack of discipline; indeed, high framework coupling is seen as the Rails way.
Framework coupling sure, but that has little to do with adding other random dependencies. Also why would you be afraid of coupling to the framework? It's not like you're going to be able to change the framework after the project grows, anyway.
For all the complaints of slow tests, the Rails community is reluctant to decouple from the framework, which is the root cause of the issue. To me, that is lack of discipline: choosing the framework way (e.g. tribal identity) over engineering integrity.
It may be that slow tests are just easy to complain about, and there isn't much business value in doing that. Totally fine. But, other things come to mind: weird cottage industry of gems that did dubious things to speed up tests (and were prone to breaking), the skepticism around interactors, the hegemony of active record (the pattern). None of those are bad things, but they reinforced the fact that the technical values of the Rails community do not work for me.
Re: Ruby on Rails: The Documentary [video]
#234This doc and the Elixir doc don't really capture much imo. They are short and hardly get the origin stories told before ending. There isn't much to get excited about before they are over, and they feel kinda like they exist to stroke the egos of those appearing in the film, and not so much to show the community or more importantly the people outside of the community, how awesome these things are. Give me a 1.5 hour l…
very different from my perception - from unusual davids approach was to how the rails team formed through Toby and the others, merging with that other frameworks... so many small bits of history that are hard to digg up anywhere
I wouldn't mind it being longer but it's great they were able to put it together
Re: Ruby on Rails: The Documentary [video]
#235I had a lot of fun watching this documentary. The one person framework really comes out in the personal story of Toby from Shopify. "From Hello World to IPO". What I also loved is that he mentioned that if you open up any Rails application, it looks basically the same in structure whether it is the biggest Rails app there is or a new one. Sure that can be true for many apps, but in a world of, for example, APIs and f…
>if you open up any Rails application, it looks basically the same in structure whether it is the biggest Rails app there is or a new one I've never worked with Rails, but this sounds amazing. One of the things I really hate about the Node.js ecosystem is that there are no clear conventions, the structure is always different even when the same framework is used. It's a mess. The exception is probably Next.js but it's…
[dead]
Re: Ruby on Rails: The Documentary [video]
#236Earlier quoted context omitted.
>if you open up any Rails application, it looks basically the same in structure whether it is the biggest Rails app there is or a new one I've never worked with Rails, but this sounds amazing. One of the things I really hate about the Node.js ecosystem is that there are no clear conventions, the structure is always different even when the same framework is used. It's a mess. The exception is probably Next.js but it's…
True, nodejs really doesn't have _the_ framework. Python had flask, php is WordPress and RoR. Why is that? Especially since most of the new frameworks copy the ideas of existing frameworks. P.S. Perhaps because a JS framework based off the ideas of rails would be called jails! /s
We have Sails which was inspired by Rails
Re: Ruby on Rails: The Documentary [video]
#237Earlier quoted context omitted.
Laravel would be a better example for PHP, especially as it borrowed so many ideas from Rails.
I agree. The only frameworks I’ve found about as productive as Rails are Laravel and Phoenix. Django and Sails.js both seemed like they were a step down in terms of general productivity, though each had a unique advantage of their own (admin out of the box, websockets & realtime features). I haven’t had a chance to really give RedwoodJS a trial run, but it's the JS-based fullstack framework I'm most curious about.
I have been using Sails since 2018 and it’s what feels close to Laravel for me and the way I keep coming to for building on the web.
Re: Ruby on Rails: The Documentary [video]
#238Earlier quoted context omitted.
True, nodejs really doesn't have _the_ framework. Python had flask, php is WordPress and RoR. Why is that? Especially since most of the new frameworks copy the ideas of existing frameworks. P.S. Perhaps because a JS framework based off the ideas of rails would be called jails! /s
I've wondered about this for years. Express was the default with Node for some years but it was mostly used for APIs to feed front ends. These days lots of people have switched to Fastify but again mostly for APIs. There's really nothing fullstack in the JS world that can be compared to Rails, Laravel, or Django. Current fullstack solutions (Next, Nuxt, SvelteKit, etc) in JS are trying to kludge front end components…
[dead]
Re: Ruby on Rails: The Documentary [video]
#239Two figures that inspired me were missing, why the lucky stiff and Ryan Bates from railcasts fame. Otherwise great docu with DHH "f*uk you" slide which does give an insight into successful open source projects.
I wouldn't expect to be mentioned in the documentary, but thanks for the shout out. :)
We (Rails programmers) appreciated all your amazing content and skills as an educator Ryan! A well-deserved Ruby Hero award recipient.
Re: Ruby on Rails: The Documentary [video]
#240Earlier quoted context omitted.
Thanks! Glad to help.
Thanks Ryan. You made me love Rails and to be passionate about coding. I’m still working every day in it and still love it every single day. I have a one man SaaS that is providing for me and my family for the last 9 years. You played a big part in it. Thank you!
Mind sharing your sass business, or the category? Always inspiring to hear about those.