Comments on https://lichess.org/@/likeawizard/blog/tofiks-v110/2NRuVZ4S
Hello, is 1K ZX chess still in use, or it's in the bin?
@Nevin_T007 said in #2:
> Hello, is 1K ZX chess still in use, or it's in the bin?
It's more than 40 years old software written for legacy hardware. But to answer a different question - some people still take pride in writing chess engines in as few lines / bytes as possible. Though usually they ignore promotions, castling, en passant and even rigorous rules on leaving your king in check.
I have an en passant in mine. And illegal move checker.
@Nevin_T007 said in #4:
> I have an en passant in mine. And illegal move checker.
I never really cared much for tiny code challenges - solving a problem in the least amount of bytes. I do not wish to discredit the skill it takes to do it but I simply enjoy writing clear and simple code.
At some point the optimization is not for make it easy for the CPU to deal with the code, but for the humans to be able to modify it intelligibly. sometimes even from one developer to another (but also, I think this op is about sharing own discoveries while developing, or having a code that is robust to some tight turn at concept level (has had in the past). so intelligible even to self might be a safe strategy. I think a previous similar attempt might have been , damn i forgot. It was made to illustrate many heuristics legibly in the code. We need code that can be analyses from a chess point of view. None of the best engine tournament are. It may be time to optimize somethings else that those context dependent ELOS.