Nice that it detects valid moves, But it doesn't know about checkmate? https://chess.maxmcd.com/r1b1kRnr/p1ppB2p/n2P2p1/8/7P/1p6/PP... Should say checkmate?
Fork it!
Static Chess
61–70 of 127 posts
Re: Static Chess
#62Is there a valtown for Python?
Re: Static Chess
#63This isn't really static right? It's still dynamically rendered by the backend each time you request the page. There aren't 999999919291293923 pre-rendered pages living on a server somewhere.
Re: Static Chess
#64Earlier quoted context omitted.
Chess960 also has different castling rules from normal chess though, and the site can't know it should use those just from the FEN?
That depends - Chess960 doesn't have different castling rules from normal chess, it just has additional considerations that normal chess does not. In other words, Chess960's castling rules are completely consistent with normal chess castling rules, so depending on how it is implemented, it might just work.
It depends on how exactly you define it. If the standard rule is as commonly taught "king moves two spaces and the rook hops over", 960 isn't the same. If the rule is "king moves to c or g file, rook moves to d or f", then it is the same. Those rules are equivalent for standard chess but only the latter ports to 960 properly. (We're probably agreeing, in that's what you mean by depending on the implementation, I'm just spelling it out.)
Re: Static Chess
#65Earlier quoted context omitted.
it would be cool if the url was just the chain of the moves. then you just paste the move chain in the URL and you get the board state.
It uses the FEN, which is the standard notation for chess positions. And it's the right choice, IMO -- if two positions are the same they should have the same URL, regardless of the specific move order used to reach it.
The move order matters, for detecting threefold or fivefold repetition, or the 50 move draw limit.
To adhere to that properly, you need to somehow represent all previous positions that could be reached again, and the number of times it has occurred. Of course you can get that by including all the move history, but it's also possible to prune it a lot, like any capture or pawn move can flush the history since no previous position is reachable. But it's still a bit more complicated than just representing the current position.
FEN doesn't account for this, deliberately leaving the history out of scope. It's a matter of preference whether you'd want a tool like this to handle those cases.
Re: Static Chess
#66Earlier quoted context omitted.
That depends - Chess960 doesn't have different castling rules from normal chess, it just has additional considerations that normal chess does not. In other words, Chess960's castling rules are completely consistent with normal chess castling rules, so depending on how it is implemented, it might just work.
It depends on how exactly you define it. If the standard rule is as commonly taught "king moves two spaces and the rook hops over", 960 isn't the same. If the rule is "king moves to c or g file, rook moves to d or f", then it is the same. Those rules are equivalent for standard chess but only the latter ports to 960 properly. (We're probably agreeing, in that's what you mean by depending on the implementation, I'm ju…
Indeed - perhaps you could say that 960's castling rules are a superset of normal castling rules.
Edit: Actually, I think the other way around is more accurate - 960's castling rules are a subset of normal castling rules.
Re: Static Chess
#67Earlier quoted context omitted.
it would be cool if the url was just the chain of the moves. then you just paste the move chain in the URL and you get the board state.
It uses the FEN, which is the standard notation for chess positions. And it's the right choice, IMO -- if two positions are the same they should have the same URL, regardless of the specific move order used to reach it.
No it shouldn’t. Move history has to be encoded so draw by threefold / fivefold repetition and fifty moves / seventy five moves can be claimed / detected.
Re: Static Chess
#68This isn't really static right? It's still dynamically rendered by the backend each time you request the page. There aren't 999999919291293923 pre-rendered pages living on a server somewhere.
Static as in no XmlHttpRequest.
Re: Static Chess
#69This isn't really static right? It's still dynamically rendered by the backend each time you request the page. There aren't 999999919291293923 pre-rendered pages living on a server somewhere.
Static as in no XmlHttpRequest.
I can start a game on Lichess, resign it right away, enter analysis mode, then disconnect from the internet and continue to use the board (in the same way that one can use the board on site we are discussing here), so Lichess's analysis board does not use XmlHttpRequest either.
Re: Static Chess
#70This isn't really static right? It's still dynamically rendered by the backend each time you request the page. There aren't 999999919291293923 pre-rendered pages living on a server somewhere.
[deleted]