undefined | Better HN

0 pointsdpc_pw7y ago0 comments

GUI programming is used as an example every time someone is praising OOP. And it seems the only time where there is some merit behind using OOP.

Chess game would be a good example of what to never do with OOP. If you start with `class Pawn inherits from Piece`, then you going to find yourself in deep shit, really fast. Low performance, high complexity. If you use an 8 by 8 array of integers that mark the pieces, than your code will be just bunch of simple algorithms, that can work really well and fast.

It might be a good exercise: write simple chess engine in OOP vs data-centric style, and compare.

0 comments

FreeFull7y ago

Even better, a chess board has 64 squares, so you can use a single 64-bit integer to store, say, the position of all white pawns, and repeat this for all the kinds of pieces. Then, you have a compact and fast data representation for your chess engine.

dpc_pwOP7y ago

The important part is - the way you represent the data matters a lot, and almost any representation will make more sense than bunch of "objects" scattered around.

j / k navigate · click thread line to collapse