#349 Rails Modularity pro
May 09, 2012 | 13 minutes | Performance, Models, Rack
Rails is a modular framework allowing you to include only what you need. Here I show how the smallest Rails app works, and then I take a look at how to whittle down a full Rails application stack.
- source codeProject Files in Zip (133 KB)
- mp4Full Size H.264 Video (40.6 MB)
- m4vSmaller H.264 Video (18.1 MB)
- webmFull Size VP8 Video (18.1 MB)
- ogvFull Size Theora Video (39.6 MB)
Well, you showed the Rails Sexuality :)
Very nice done! Thank you!
This is by far the most interesting episode so far. It makes me feel good about being a subscriber to the pro series. Thank you.
ditto, and there have been some damn good episodes over the years
Thank you Ryan. Very well job.
I like this episode a lot. Nevertheless, here's the inevatibable "but":
What first came into my mind when I was reading the headline was something like stripping down Rails itself into its components.
I see your point in trying to get to a minimal rails application. Yet, you would still have to install the full rails stack.
But would it also be possible to have a minmimal rails app running with only those modules installed, that are actually required by the application?
Where one might eventually end up with somthing like Sinatra for micro appslications?
Hey Ryan, I'm new to Rails and this is exactly the type of thing I was working on doing a few days back :)
Primarily, because I learn by deconstructing, and I definitely, found too much noise + magic so far;
Please continue diving into Rails internals as this should be elucidated to the community as much as possible (it probably is I guess, but you also end up tremendously easing adoption by newcomers)
Thanks Ryan, definitely a good idea to dive into internals.
Thank you for this excellent episode! One of the most eye-opening ever.
This episode was a catch of a fresh air for me. Now I have a better understanding of rails modularity.
This was a really awesome episode. Starting with a bare bones app and plugging in modules when I need them makes more sense to me than starting with everything but the kitchen sink then pulling out (in a sort of error-proned way) what I don't need. I am new to Rails and I was curious why Rails has --skip-[module name] options when creating a new app rather than --include-[module name] options. Now I understand why I've seen discussions on some blogs about Rails becoming too "big". Now I know (thanks to this episode) that's not the case; Rails is just delivered that way.
such impress. very thanks.
I think this is one of the very few resources out there that explains how rails is constructed. And it does so in the Ryan Bates's concise-yet-thorough style.
Having this primer will save so much time reading through the rails source code.