I'm teaching myself Merb. It's superficial resemblence to Rails [1] can trip me up.
For example, associations.
Ruby
Merb
What this means is I gotta go look stuff up instead of assuming, which is good for me but man it can frustrating.
[1] serves web pages, has ruby running around on the back end.
For example, associations.
Ruby
has_many :articles
Merb
has n, :articles
What this means is I gotta go look stuff up instead of assuming, which is good for me but man it can frustrating.
[1] serves web pages, has ruby running around on the back end.