Samuel
@samuel.fm
another day another mysterious load-bearing console.log
3 1 73
Samuel
like, wtf.... it's calling updateLayout() to tell the native side to re-adjust the sheet height. if you add a console log before or after, it's instant
5 2 18
dan
maybe not the most fun suggestion but keep in mind you can keep bisecting inside of console log implementation (starting with JS side and then into native side) to find what actually makes the behavior different
1 7
dan
basically adding early returns at every layer and checking when the the behavior flips
1 6
Samuel
ah nice - if we comment out the part where it sends the logs over websocket to the CLI, it's broken again
1 6
dan
now the question is whether the contents being sent is important or just a websocket operation, whether it matters if there’s a websocket message recipient or just receiving is somehow enough
1 2
Emelia
iirc, sending over a websocket may happen in a microtask, much like fetch, so that might be causing a difference in paint times?
Orual
ive had them on microcontrollers with no out of order instruction execution or threads so
1 7
advaith
one of our rust services always crashes when I run it, unless I add a print on the line before the one that crashes
1