Recently, I started digging into design patterns. Generally speaking, I thought that the design problems that most design patterns solve usually do not occur in Ruby. Most of the design problems were due to data types (without dynamic typing and arrays, objects belonging to one class at a time, etc., etc. can be stored. Being a ruby and a ruby on the rails developer, I realized that there are no concepts of interfaces, abstract classes, links, pointers, etc. And the presence of concepts such as modules, dynamic typing, an array with objects of any class together, functions such as eval, for developers. I also reviewed the book by Rus Olsen. However, I thought the book was trying to mimic design patterns instead of actually implementing them, because design problems just didn't occur in Ruby. Is it that the Ruby programming language has evolved over time and takes care of design issues, which is why developers are more focused on business logic?
I would like to know the opinions of other Ruby developers about this. Thanks.
source
share