scalachess VS ramda

Well, only since this year, it seems.

From another reddit thread I got the link to the commit with the fix. Thankfully, they did add a test case for this: https://github.com/lichess-org/scalachess/commit/f5218340b2a229fa519ecd239fe50aee722bcd0f

To be fair, that TODO has only been there for three weeks, which seems reasonable, especially considering it was written by a volunteer.

Lichess does not check for mate. It simply doesn't consider KBvKN a drawn endgame.

https://github.com/lichess-org/scalachess/tree/master/src/ma...

It's funny because I remember comparing it to mine that I had tried to write during college, and appreciating how much better it is.

Pay attention to how there's a bunch of different types of chess in there too, and how that's factored.

The Lichess implementation is as follows:

The Lichess implementation does not fully comply with those rules. It looks strictly at the material on the board.

For reference, here's the current implementation.

JavaScript is great for point-free programming! Make sure you check out Ramda.js https://ramdajs.com/

It’s fun in the sense that solving a puzzle is fun, but I avoid it for anything I need to maintain long-term.

But it’s good practice for understanding combinators which is useful for some kinds of problems.

This is very cool. I remember I got sucked into things like Ramda going down this functional programming rabbit hole :-)

https://ramdajs.com/

To create our pipeline, I'm going to use the pipe function from the NodeJS ramda library instead of building my own.

Other libraries to check out are pratica and ramda

I recently took ownership of the new types/ramda repo. This repo is re-exported by @types/ramda and is the first step to bringing type definitions for ramda in-house. We're already hard at work correcting major issues, adding full currying support, and general bug fixes

I'm going to be honest. You probably don't need to use currying in JavaScript. In fact, trying to fit it in your code is going to do more harm than good, unless it's just for fun. Currying only becomes useful when you fully embrace functional programming, which, in JavaScript, means using a library like Ramda instead of the standard built-in functions.

Lodash gets so many things wrong I’d rather not see it in most projects. I appreciate a good utility library for JS projects but my go-to choice has to be Ramda[1]. Every function it exports is curried and works great with pipe which enables me to write highly reusable and composable functions in pointfree notation. I have never been as productive with lodash, and I find the functional style easier to read

[1] https://ramdajs.com/

Do note though that ramda is different from rambda. 👍 (Granted they are very similar!)