Can Ruby really have design issues that the design patterns solve? -

I have recently started digging in design patterns generally speaking, I thought that the issues of design, which Most design issues were due to datatypes (no dynamic typing and arrays can hold objects of the same orbit at a time etc.) and that the design patterns of most are not generally in Ruby. Many more Being Ruby and Ruby on the Rail Developer, I realized that the lack of concepts and concepts of interface, abstract classes, references, pointers, etc., features like dynamic typing, array of objects with any class objects, such as Eval actually makes life easier for developers. I went through too, though I thought, that the book actually designs instead of applying them to Pat Attempted to simulate the N, due to design issues within Ruby usually not. Is it that, the Ruby programming language has evolved over time and internally takes care of the internal design issues that focus on the business logic of the developer?

I want to know the views of other Ruby developers on this. Thank you.

Naturally, And the system differs in the system. Ruby can really solve some of the problems in other languages, but it will usually generate problems of its own problems.