Ruby On REST: Introducing the Representer Pattern

Ruby On REST: Introducing the Representer Pattern:

The calls for more object-orientation in Ruby frameworks are growing ever louder. Most web frameworks, like Rails, come with a nice database abstraction, a Rack-like HTTP endpoint, routing, and a template engine. It’s the lack of additional abstraction layers that make many programmers ask for “more OOP”.

[Yeah, been feeling this for a while. The problem is unless you can put in some serious refactoring to an established project the weight of getting things done (momentum) often overwhelms the desire to improve the codebase (which, of course, makes the future refactoring larger in the ugliest of loops).]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s