Not to undermine the usefulness of OOP, IMO, I think the usage of OOP is greatly overrated.
It's useful when used effectively.
I think OOP is useful when working with resources, in other words, you cannot have many instances because of the "cost". :)
Disclaimer: I'm not a trained software engineer but more like a hardware guy, the dataflow between modules is easier for me, and it's more straight forward compared to triple inheritance style and unnecessary classes definitions
mashingan, cdome,
I think radagasts request is a valid point, as very many people are used to OOP design. Most of that needed information seems to be available, but it is distributed and maybe not well enough explained to not really bright coders.
But explaining all that well would be 50 to 70 pages in a Nim textbook. Maybe followed by an example which shows conversion of a OOP program to a non OOP Nim one discussing the benefits. Maybe 15 pages more. I guess the bright developers have more important task to do currently, and Nim still evolves...