Why didactic chess engines are DOOMED to be SLOW & WEAK - bitter experience almost made me give up
Hey what's up guys, Code Monkey King's here. I'll start this video by sharing the latest improvement in the move generator of my wukongJS chess engine and then explain the difference between optimization for clarity vs speed & strength.
CONTENTS:
00:31 demo of twice faster move generator compared to the previous video
01:32 improvements overview (backup in stack VS backup on the fly + bugfix)
05:38 how fast it should be (comparison with VICE JS)
06:05 updates in writing move list
08:47 running perft via nodejs
09:08 write on your own VS copy/paste (I was close to drop chess programming)
10:24 why DIDACTIC chess engines are SLOW & WEAK
11:34 make move function in VICE overview & comparison with my own
17:31 overloaded functions & overall architecture issues
18:58 why I didn't follow "best practices"
20:33 how DIDACTIC engine different from those written for SPEED & STRENGTH
22:47 why did I pick up didactic approach initially
26:59 optimizations for SPEED & STRENGTH are TOTALLY DIFFERENT compared to DIDACTIC ones
38:10 Why didactic engines are DOOMED to be SLOW & WEAK
30:21 Why SOLID PROGRAMMERS writing STRONG chess engines ARE NOT going for YouTube?
32:13 WHAT stops me from creating a STRONG chess engine???
34:41 DIDACTIC chess engine would remain DIDACTIC until the dying day)
35:37 two completely DIFFERENT PATTERNS in chess engine development
36:18 my chess engine is DOOMED to be SLOW & WEAK...
36:46 SO WHAT ON EARTH TO DO THEN???
SOURCE CODE:
https://github.com/maksimKorzh/wukong...
Track WukongJS development progress:
https://maksimkorzh.github.io/wukongJ...