How do you handle logging then? If f() calls g(), how can I add logging to g() without having to change or recompile f() (and everything in the call stack above it)? ‘You can’t’ is not an acceptable answer.
1,162 karma · joined May 24, 2010
How do you handle logging then? If f() calls g(), how can I add logging to g() without having to change or recompile f() (and everything in the call stack above it)? ‘You can’t’ is not an acceptable answer.
That's a very, very small target you're aiming at there.
Oh my god thank you. I've been trying to wrap my head around the whole async/await paradigm for years, basically writing code based on a few black magic rules that I only half understand, and you finally made it all clear in once sentence. Why all those other attempts to explain async/await don't just say this I can't imagine.
Eloquence for the ages.
2. But the whole point here is that others aren't doing this any more. Threads isn't supposed to be an innovation, just a Twitter replacement. Twitter is dying, Mastodon is too complicated for non-geeks, BlueSky could have been a contender but they didn't get their act together quickly enough.
3. You're in a geek information bubble here. On the scale of social media, almost nobody cares about that sort of thing. I'd bet money that the overwhelming majority of FB users have never even heard of Zuckerberg.
(looks at map of Pacific)
Hang on ... where did the earlier ones stop?