OpenSourceChess VS dupver

I went with a single set of recursive functions for the moves: https://github.com/herval/OpenSourceChess/blob/main/Assets/Scripts/Piece.cs The nice thing is I can model any movement with this (except something crazy like a hypothetical piece that’d bounce on walls)

Its actually mentioned in the readme: https://github.com/herval/OpenSourceChess

I'm making an open source Chess game, mostly to learn Unity: https://github.com/herval/OpenSourceChess

Publishing binaries on itch as it evolves too: https://herval.itch.io/open-source-chess

I'm forcing myself to work one hour a day on it (at least two Pomodoros) no matter what, which is a nice change of pace to my day job (in management), and really adds up over time. I gave up on starting games many times in the past, because it always felt so overwhelming to start from a blank page, and I'm already starting to build up the understanding to tackle on some actually more original game next :-)

I work with a lot of uncompressed structured binary files so I finally broke down and wrote my own system based on the Restic chunker: https://github.com/akbarnes/dupver

I wound up writing dupver https://github.com/akbarnes/dupver after getting frustrated with the lack of versioning tools for binary files. One neat thing about .docx files and their ilk is that they are "just" zip files so it isn't hard to add special handling to pull out their contents and run deduplication over that.

DupVer https://github.com/akbarnes/dupver is a deduplicating version control system for large binary files. It's designed to keep state in a repository on the local machine separate from the working directory so it plays nice with cloud synchronization software.

I started it after constant headaches involving Git LFS and the corporate proxy. It's based around the Restic chunker library, with inspiration from both the Duplicacy backup software and Boar, another binary version control system for large binary files.

https://github.com/akbarnes/dupver