sleek sun
Hi!
Thanks for the great work, I love speedtest in 17.1
MY problem/observation is that in the browser environment the output of speedtest looks really ugly (std::cerr is mapped to console.error)
https://github.com/official-stockfish/Stockfish/blob/master/src/uci.cpp
I studied above source code and I found it is probably because you use stderr for not standard UCI output?
I was using the lichess wasm to see the speed difference between native cpp stockfish and the browser wasm and first I thought there is an error in the wasm but I waited and at the end the test output looked just fine, only in error red 🙂
Should we just accept this because it is a deeper design decision or would it be a problem to change UCIEngine::benchmark function in uci.cpp to use std::cout instead of std::cerr for printing?
Or if we change something the right way is to change the code before converting the code to wasm?
I researched a bit with AI and it says stockfish probably wants to separate different kind of UCI output and there could be even a logic on a UI program, for example, that uses this. But is this true for speedtest too? At present I dont understand what speaks against normal output for speedtest.
Thanks!
versed hound
