Data source: swyx's twitter data
id | user | created_at | full_text | retweeted_status | quoted_status | place | source | truncated | display_text_range | in_reply_to_status_id | in_reply_to_user_id | in_reply_to_screen_name | geo | coordinates | contributors | is_quote_status | retweet_count | favorite_count | favorited | retweeted | possibly_sensitive | lang | scopes |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1201528574236217345 | 33521530 | 2019-12-02T15:48:30+00:00 | One thing I wish I learned way earlier in my JS journey is Node Streams and child processes. We use them *all the time* in our tools but because this isn't in introductory material it seems "advanced". Two helpful articles: - https://medium.com/edge-coders/node-js-child-processes-everything-you-need-to-know-e69498fe970a - https://2ality.com/2018/05/child-process-streams.html | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 277] | 0 | 75 | 311 | 0 | 1 | 0 | en |