News for hackers. Stuff that matters.
Re:Lichess Analysis Board with Stockfish 8 in Asm.js by boarquantile on Monday June 12, 2017 @07:10AM (#14536333)
Lichess tries to use (in this order): PNaCl, WASM, asm.js.

PNaCl required almost no modifications to Stockfish (https://github.com/niklasf/stockfish.pexe), supports multithreading and is still the fastest.

WASM and asm.js require the same patches (https://github.com/niklasf/stockfish.js). Most notably WASM does not yet have multi-threading. In the original Stockfish one dedicated thread is listening for new commands. Instead now the main search thread (since it's the only thread) has to check for new commands from time to time, which costs a bit of performance.

Re:Lichess Analysis Board with Stockfish 8 in Asm.js by fortytw2 on Sunday June 11, 2017 @03:29PM (#14533367)
The repo for stockfish.js can be found here https://github.com/niklasf/stockfish.js

(maybe someone more familiar with the lichess architecture could go into a bit more depth here)

Re:Lichess Analysis Board with Stockfish 8 in Asm.js by lern_too_spel on Sunday June 11, 2017 @07:14PM (#14534332)
Lichess also supports PNaCl Stockfish on Chrome for multithreaded analysis.
Re:Lichess Analysis Board with Stockfish 8 in Asm.js by sharifm on Sunday June 11, 2017 @04:10PM (#14533522)
WebAssembly is supported as well. It has become much faster a few months back when it supported WebAssembly. On my system and using forefox it was 340 knodes/s with asm.js. With WebAssembly it is 600+ knodes/s
Re:Lichess Analysis Board with Stockfish 8 in Asm.js by grondilu on Sunday June 11, 2017 @08:15PM (#14534530)
Weirdly enough, I was thinking webassembly but I wrote asm.js. I'm very surprised this happened, but apparently it did.
Re:Lichess Analysis Board with Stockfish 8 in Asm.js by thope on Monday June 12, 2017 @05:28AM (#14536006)
Actually 'WebAssembly' appeared in the title for few minutes, but then it was edited to 'Asm.js'
Re:Lichess Analysis Board with Stockfish 8 in Asm.js by grondilu on Monday June 12, 2017 @11:22AM (#14538000)
I was suspecting so. I presume whoever did it followed the link, noticed the engine was using asm.js and not wasm, and thought I was mistaken. But truly what the engine uses depends on the browser and its configuration.