This is because console.log isn't the equivalent to the post's printf. It is purposefully opaque to the application (and applications should not assume anything

This is because console.log isn't the equivalent to the post's printf. It is purposefully opaque to the application (and applications should not assume anything happens with the input).[0] > Its main output is the implementation-defined side effect of printing the result to the console. [0]: https://console.spec.whatwg.org/#logger https://console.spec.whatwg.org/#logger