21–30 of 31 posts
You need to switch your data representation to 0x88 [1] or bitbords [2] to get anything performant. You won't get anywhere with a class hierarchy [1] https://www.chessprogramming.org/0x88 [2] https://www.chessprogramming.org/Bitboards
I cut you this one issue, https://github.com/jaeheonshim/ChessBoard/issues/1
I think your castling logic is incomplete? Worth a double check.
As someone who has implemented online multiplayer tbs games before, this is exactly the kind of thing you would use at the backend. However, you also need the same code running on the frontend in order to do validations before sending moves to the backend. That optimization helps distribute some server load and gets you immediate feedback. In Java's case, I'd use some java to js or java to kotlin to js transpilation.
Is performing chess validations that heavy, if you're serving ~10,000 games? (just asking for a friend)
I'd encourage you to get involved with the passionate community at talkchess: http://talkchess.com/forum3/index.php
And join a small group on IRC at Freenode ##chessprogramming where we discuss chess AIs, libraries and often other games like Ataxx and Go.
I myself am an author of a chess library: https://github.com/Mk-Chan/libchess ! Great to see development for Java as well
You need to switch your data representation to 0x88 [1] or bitbords [2] to get anything performant. You won't get anywhere with a class hierarchy [1] https://www.chessprogramming.org/0x88 [2] https://www.chessprogramming.org/Bitboards
You need to consider the goals of a project before giving advice.
You need to switch your data representation to 0x88 [1] or bitbords [2] to get anything performant. You won't get anywhere with a class hierarchy [1] https://www.chessprogramming.org/0x88 [2] https://www.chessprogramming.org/Bitboards
If the API is well written, this is an implementation detail.
Earlier quoted context omitted.
You need to consider the goals of a project before giving advice.
OP mentions chess AI and game analyzer. Those would benefit from an optimized data representation.
Competing with the state of the art is not an implicit goal for every project.
Earlier quoted context omitted.
Is performing chess validations that heavy, if you're serving ~10,000 games? (just asking for a friend)
To do all validations and move suggesions on the server side causes data traffic for no reason. Not just cpu time. It is senseless.
Earlier quoted context omitted.
If the API is well written, this is an implementation detail.
Well, it depends on the project goals. For a GUI app I can agree but good luck writing a chess engine where data representation is hidden behind an abstract interface.