-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
About "TL;DR" in the article as the title #2210
Comments
ghost
added
the
discuss
label
Apr 28, 2019
@nodejs/website:What do you think of this? |
An alternative title might be "Executive summary" or "Abstract" or similar. |
Yeah, it basically means "Summary". |
ghost
mentioned this issue
Apr 29, 2019
ghost
pushed a commit
that referenced
this issue
May 1, 2019
Ref: #2210. In order to give a good understanding of 'TL;DR', change it to 'Summary' to make it more proper.
ghost
closed this as completed
May 1, 2019
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just a question about this fixed phrase at (https://github.com/nodejs/nodejs.org/blob/master/locale/en/docs/guides/dont-block-the-event-loop.md#tl-dr), because this phrase explains the process of Nodejs in the event and how to improve the speed of Nodejs' work.
I don't know why "TL;DR" for this phrase? Why does it mean "Too Long Didn't Read"?
So IMO the title should be something like "What to notice for improvement of efficiency for Nodejs in the event loop?"
The text was updated successfully, but these errors were encountered: