Documentation Writes a Paragraph to Avoid Saying 'Callback'
Description
A two-panel webcomic from WebDevToons (#242 - CALLBACK, by gfcf14, @webdevtoons). In the first panel, a dark-haired character in a green shirt looks at a monitor labeled 'SOME DOCUMENTATION I FOUND:'. The screen shows a React code snippet using this.setState({ isLoggedIn: true }, () => { console.log('User is logged in.'); }) and a verbose highlighted 'Conclusion:' paragraph reading 'The second argument of the setState() function in React.js provides a powerful mechanism for handling state updates and executing code after the state has been updated and the component has re-rendered...'. In the second panel the exasperated character shouts: 'WHY CAN'T YOU JUST SAY `CALLBACK`?!'. The comic mocks bloated, likely AI-generated documentation prose that dances around a simple, standard term every developer already knows
Comments
10Comment deleted
That paragraph has the same energy as a junior's PR description: 200 words of 'powerful mechanism', zero words of what it actually does
The callback finished before the documentation got to the point.
+15 tokens Comment deleted
Mentioning re-render is important, other is filler words. But the 2nd sentence actually looks worse to me. It provides exactly ZERO VALUE. First at least is some infromation Comment deleted
Callback is C thing, therefore mentioning it makes documetation less safe Comment deleted
Monad is just a monoid in the endofunctor category Comment deleted
You can't say it's a callback or else people would instinctively try to promisify it Comment deleted
This plus hipsters not liking this word hence why react was created in the first place Comment deleted
Indeed.. replace powerful with callback. Comment deleted
Your comprehension is not the goal. It's avoiding liability Comment deleted