It's definitely the buffer reuse. Memory allocation is the slowest thing in the world apparently.
Are you benchmarking against my latest commits on go-nostr? Because on these I have copied your string unsafe trick so it's not fair.
Just don't wake up the C and Rust boys @jb55 and @Mike Dilger ☑️ or they will smash us with their faster code.
Thread
Login to reply
Replies (1)
of course, i started this after you made these changes... and i am happy to discover a big waste in my code... i mean epic
also, it does still log now, just not the super complicated shit i had before, even still adds ascii colour to make the links blue on VTE
also, bring it on!
i bet i can make Go code that is within 1%, a recent code contest showed that current Go version was neck and neck with the best algorithm written in java, though i'm sure you realise that is like comparing oranges and tangerines, still, java is not far behind C++ in most things