DHH, as you probably heard, has learnt to stop worrying and love the CRUD. I’m very much in agreement. The idea of replacing the actions add_member and remove_member (or would that be join_group and leave_group?) with Membership#create and Membership#destroy was the final light switch that got me to a place I’d been striving for.
The generic controller. A standard implementation of the CRUD actions that can be used out-of-the-box in a large majority of cases.
DRYML: The Dont-Repeat-Yourself Markup Language. In case you hadn’t guessed, we’re intending to bring a higher level of re-use to Rails’ views.
Why? Rails already has a bunch of mechanisms for re-use within views. Namely: layouts, partials and helpers. Each serves a different purpose, and yet, IMHO, there’s still a gap. I find that small fragments of mark-up tend to crop up over and over in my views. Yes I could extract them into paritals or helpers, but I find myself disinclined to do so.
Bud Fox: How much is enough?
Gordon Gekko: It’s not a question of enough, pal. It’s a zero sum game, somebody wins, somebody loses. Money itself isn’t lost or made, it’s simply transferred from one perception to another.
I’m a bit of a Gordon Gekko myself when it comes to programming. Greed is good. Remember? Greed works. I’m greedy for speed. Seems to me pretty reasonable that I should be able to build a nice looking, usable, fully-ajaxified database app in what? A couple of hours? That would be fast enough. Then I’d be satisfied [grin].
Find what you're looking for quickly by using our keyword search. Can't find it? Try our links below.