this is a bit of a mischaracterization of what's being claimed in the post, all they were saying about binary sizes is that their updates have resulted in SMALLER binary sizes when compiling compared to the previous versions, i.e. they're noting an improvement. nowhere on this page nor any linked from it do they claim they make "small binaries" (that i can find! could be wrong), and you even had to click through their example dedicated to noting this improvement to find the 58mb number you keep mocking.
if you wanted to argue that point, I'd suggest you compare the other solutions that exist today to compile nodejs projects into single executable binaries to be able to have a discussion on why you consider their progress lacking. it's a reasonable point that disqualifies a lot of use cases for these types of tools, but I don't think the conversation was framed from that perspective.