Hacker News Reader

Comment by DeathArrow | Hacker News Reader

Functional or procedural or whatever, it doesn't matter much for me as long as the paradigm is not OOP.

I strongly believe that data should live separate from the actions performed on it. I also believe that inheritance is a bad thing as there are other, better means to achieve polymorphism.

I do believe in a data oriented programming where we waste as little CPU cycles as possible and introduce as little abstractions as possible.

View on HN

I am working on a java game where I threw all OOP knowledge out the window and use C-style pure data-classes with public fields and no methods.

It's pretty refreshing to work this way compared to the design pattern madness you see in enterprise applications - but I guess it's not very safe if multiple people are working on this and some don't know what they are doing.

There has to be some middle ground, I think people have been going way overboard with OOP in the last two decades.

Me too, I use .NET but try to use in the least OOP way as possible. Of course, for interviews I can recite all things about OOP, countless patterns and their "advantages", SOLID, DDD done OOP way and most of the Uncle Bob "wise" teachings.

I dunno, even in C codebases, it's not uncommon to have data structures containing function pointers. Polymorphism isn't inherently bad and trying to achieve it using, say, enums and big switch statements isn't particularly maintainable.

Reply on news.ycombinator.com