Stockfish VS tigerbeetle

The Stockfish program can be set to play at strength level 0-20. Estimates of the levels' Elo is provided here: https://github.com/official-stockfish/Stockfish/commit/a08b8...

- and handicapped Stockfish (https://stockfishchess.org).

The whole thing is at https://github.com/magv/bchess, and can be installed with just 'pip install bchess'.

This was the result searching for all the 35 stockfish benchmark positions to depth 6.

Stockfish doesn't have a classical evaluation anymore. And before this, most of the time (around 90%), NNUE was used to evaluate.

If you use ChessBase on a MacBook through Parallels, there's an issue where people have posted Apple Silicon compiles for Windows: https://github.com/official-stockfish/Stockfish/issues/4241

Progress can be found here https://github.com/official-stockfish/Stockfish/wiki/Regression-Tests At 1 thread it has gained +18.3 elo on a balanced book, and +47.03 on UHO (unbalanced) book as well as +39.4 elo for FRC and +65.56 for DFRC. At 8 threads it has gained +14.33 elo on a balanced book and +49.46 on UHO (unbalanced book). Also testing was done on 8 threads with 180+1.8 (this is considered very long time control for fishtest standards) and progress was +9.45 on balanced book and +49.65 on UHO.

Downloads are available temporarily here https://github.com/official-stockfish/Stockfish/releases/tag/stockfish-dev-20230622-a49b3ba7

The strongest version of Stockfish is the latest development version of Stockfish

I am trying to implement Stockfish (a popular chess engine) into my React Native app.

I'm waiting for someone to implement the Redis API by swapping out the state machine in TigerBeetle (which was built modularly such that the state machine can be swapped out).

https://tigerbeetle.com/

I fully agree with what Prime says at the end - Joran has really set a new bar here for all future database presentations.

Hearing that the entire TigerBeetle domain logic lives in a single file [0] (and is intended to be pluggable for other OLTP use cases!) makes it 1000% more tempting to spend the weekend getting up to speed with Zig.

[0] https://github.com/tigerbeetle/tigerbeetle/blob/main/src/sta...

Why would you want to build your own accounting ledger from scratch? Accounting is a completely new domain for most engineers, and TigerBeetle (https://tigerbeetle.com/) already solves this problem.

Maelstrom [1], a workbench for learning distributed systems from the creator of Jepsen, includes a simple (model-checked) implementation of Raft and an excellent tutorial on implementing it.

Raft is a simple algorithm, but as others have noted, the original paper includes many correctness details often brushed over in toy implementations. Furthermore, the fallibility of real-world hardware (handling memory/disk corruption and grey failures), the requirements of real-world systems with tight latency SLAs, and a need for things like flexible quorum/dynamic cluster membership make implementing it for production a long and daunting task. The commit history of etcd and hashicorp/raft, likely the two most battle-tested open source implementations of raft that still surface correctness bugs on the regular tell you all you need to know.

The tigerbeetle team talks in detail about the real-world aspects of distributed systems on imperfect hardware/non-abstracted system models, and why they chose viewstamp replication, which predates Paxos but looks more like Raft.

[1]: https://github.com/jepsen-io/maelstrom/

[2]: https://github.com/tigerbeetle/tigerbeetle/blob/main/docs/DE...

> There is no reason to use a memory unsafe language anymore, except legacy codebases, and that is also slowly but surely diminishing. I'm still yet to hear this amazingly compelling reason that you just need memory unsafe languages. In terms of cost/benefits analysis, memory unsafety is literally all costs.

Tell that to the authors of new memory unsafe languages (like Zig) and creators of new project in those languages (like https://tigerbeetle.com) :(