One of my biggest mistakes as a dev was not really learning Rails until 2015.
I just didn’t know how much faster building web apps could be.
Ruby on Rails: The Documentary [video]
11–20 of 248 posts
Re: Ruby on Rails: The Documentary [video]
#12I 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…
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
Re: Ruby on Rails: The Documentary [video]
#13This was so fun to watch. It’s great to see people find their calling and do great work and change the world for the better along the way.
Re: Ruby on Rails: The Documentary [video]
#14Earlier 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
> P.S. Perhaps because a JS framework based off the ideas of rails would be called jails! /s
Re: Ruby on Rails: The Documentary [video]
#15Two 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.
Ryan Bates is a legend
Indeed. Also, kudos to Chris Oliver for taking up the mantle. https://github.com/excid3
Re: Ruby on Rails: The Documentary [video]
#16Earlier 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
Laravel would be a better example for PHP, especially as it borrowed so many ideas from Rails.
Re: Ruby on Rails: The Documentary [video]
#17> 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 used to love this, untill I started to hate it. I am convinced this is a major contributor to why so many Rails apps turn into an unmaintainable mess over years.
Who measures onboarding in hours? It's fine if it takes a day or two to understand the domain. And the framework. And how they tie together.
Talking about the domain: Rails puts "the plumbing" up front. Its how it achieves this consistency. My app is never about "models" or "http" or "databases". My app is about medicine-journals. Or loan-request-management. Or CRM. Rails makes itself important, at the cost of my domain.
Rails' opinionatedness makes it so that this is hewn in stone. Its MVC is a given - and that's fine - major architectures should probably be dictated by the framework. But it's ORM - ActiveRecord also is a given. And that's not fine because AR (as an architecture and as how Rails implements it) is very unfit for a large category of applications. It's virtually impossible to swap AR out for anything else. Same with templates/views, JS, Caching, and many more: you can -in theory- replace them with a drop-in alternative. But you cannot -not even in theory- replace them with something that has an entirely different architecture or concept. This makes Rails not Omakase, but actually McDonalds: wherever in the world you come, you know exeactly what to expect, but it also makes boring and bland: no-one eats 7days/week McD.
This makes all Rails apps look alike. Despite the fact that not one of the apps that "we" are building is alike another. Domain. Team. Project Planning. Combine any of them and the projects demand different things, but with Rails you are out of luck. Regardless if you build the next fintech platform with a team of 120 senior devs over 6 years, or you hack your "marketplace for coffeelovers" over the weekends alone: you get The Rails Way. One of those might be a perfect fit. But it's impossible they all are. Each team gets the same "menu". And in many cases it simply won't fit.
Re: Ruby on Rails: The Documentary [video]
#18One of my biggest mistakes as a dev was not really learning Rails until 2015. I just didn’t know how much faster building web apps could be.
Yeah me too. I am still sad thinking about the number of hours I spend messing with python environments and versions because I was told it was the “quick and easy” option for solving this or that small problem.*
Also worth mentioning Michael Hart’s intro course, which is a really shockingly well done way to ramp up from absolute zero, even for someone with very little code experience.
* Which, in fairness, it mostly is. But also meh.
Re: Ruby on Rails: The Documentary [video]
#19I 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…
And lots more.
Ruby 3.3 YJIT is 2x faster than Ruby 2.5 in RailsBench.
Work on brining more Ruby Gem from C to Ruby ( easier JIT )
Lots of dev tooling around Ruby and Rails coming.
Hopefully there are more good things to come in Rails 8.0 and Ruby 3.4
Re: Ruby on Rails: The Documentary [video]
#20> 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 used to love this, untill I started to hate it. I am convinced this is a major contributor to why so many Rails apps turn into an unmaintainable mess over years. Who measures onboarding in hours? It's fine if it takes a day or two to understand the domain. And the framework. An…
I couldn't agree more. There is also a technology aspect to it. Rails is objectively veeeeeery slow. Concurrency support is nonexistent. This is not a good
fit for all problems. It also to some degree prevents you from breaking out the parts that would benefit from a different language into their own services (Rails needs to call them, but it's really not good at IO).