We’ve completely rewritten Next Chess Move’s website front-end. We hope that it’s not too noticeable aside from some tidied-up pixels here and there.
Access the new NCM on the beta site: https://beta.nextchessmove.com/
New Feature: Multi-PV Search
Multi-PV lets you caluclate not only the best move, but also the 2nd, 3rd, and up to 4th best moves for any position.
This does, however, come at a cost. Searching for multiple moves introduces computational overhead which slightly slows the engine’s depth progression. But if you want multiple move suggestions for a single position, Multi-PV search is the way to go.
We’re dropping support for Internet Explorer 10 and older. Most other reasonably modern browsers should work in NCM.
We’ve tested several browsers and versions, but there will undoubtably still be bugs. If you run in to any issue at all, please let us know and we will deploy a fix ASAP!
Why the Rewrite?
We wanted a simpler and more testable code base to make it easier to grow and implement new features. We made the following major technology changes:
- Replaced CoffeeScript with TypeScript.
- Replaced Reflux with Redux.
- Removed Bootstrap and jQuery.
Normally we introduce new technologies gradually and incrementally, but these changes, when combined, were too much. So we decided to rewrite.
Not a lot. We tried to keep everything visually similar. The desktop version is about 50 pixels wider. The settings modal has explanations for each setting, and we’ve added Multi-PV support. But other than that we hope it feels like the same old NCM.
Some of the more notable technical changes include:
- Page size has been reduced from 630KB to 212KB.
- Piece images are now inline for smoother animations and reduced network requests.
- We’re using a dedicated subdomain for mobile.
Over the next few months we’ll be focusing on:
- Addressing issues as they’re discovered in beta.
- Applying similar technology changes (and likely rewrites) to the Android and iPhone mobile apps.
After the rewrite goes to production and the apps are updated, we’ll start increasing the maximum think time beyond its current limit of 15 seconds.
How You Can Help
Please give the beta website a try and let us know what you think! You can reply to this post, open a support ticket, or email me directly at firstname.lastname@example.org.
All feedback is very much appreciated!