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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1449884413848809475 | 33521530 | 2021-10-17T23:45:56+00:00 | @noseratio @jhooks our job is executing work across time and unreliable networks and machines: https://twitter.com/threepointone/status/1449112317917110276?s=21, React’s job is rendering the most current version of app state that is ready. i guess perhaps the analogy falls down there but there’s still useful things to borrow from React. | 1449112317917110276 | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [19, 297] | 1449882287240187909 | 33521530 | swyx | 1 | 0 | 1 | 0 | 0 | 0 | en |