From SO:
OpenStructobjects are useful when you need something to fit a certain method call interface (i.e. send in a duck-typed object responding to#nameand#value), or when you want to encapsulate the implementation details, but also want to avoid over-engineering the solution. They also make an awesome stub object, and I often use them in place of framework stubs when I don’t need the overhead of a stub/mock.
You’ll just have to get over your dislike of Ruby and write a few apps in it ODL - just so you can see why so many people love it 
