The Artima Developer Community
Sponsored Link

Ruby Buzz Forum
Ruby: PORO

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Jay Fields

Posts: 765
Nickname: jayfields
Registered: Sep, 2006

Jay Fields is a software developer for ThoughtWorks
Ruby: PORO Posted: Oct 11, 2007 11:59 AM
Reply to this message Reply

This post originated from an RSS feed registered with Ruby Buzz by Jay Fields.
Original Post: Ruby: PORO
Feed Title: Jay Fields Thoughts
Feed URL: http://blog.jayfields.com/rss.xml
Feed Description: Thoughts on Software Development
Latest Ruby Buzz Posts
Latest Ruby Buzz Posts by Jay Fields
Latest Posts From Jay Fields Thoughts

Advertisement
The term PORO (Plain Old Ruby Object) is being used a bit more often these days. In a comment on my last post someone expressed frustration that I didn't validate the acronym. After a quick Google search I noticed that no one has gone out of their way to point out it's meaning.

PORO isn't a term that was born in the Ruby community. In fact the original POXO was POJO.
The term was coined while Rebecca Parsons, Josh MacKenzie and I were preparing for a talk at a conference in September 2000. In the talk we were pointing out the many benefits of encoding business logic into regular java objects...
POROs, like POJOs, are often found in discussions about simplicity and testing.
POJO is an acronym for Plain Old Java Object, and is favoured by advocates of the idea that the simpler the design, the better. --Wikipedia
There's plenty of discussion around POJOs on the web, most of which applies to POROs as well.

Read: Ruby: PORO

Topic: RubyInject Previous Topic   Next Topic Topic: Making RubyForge History

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use