tweets

This is data scraped from swyx's timeline! See blog post

8 rows where "created_at" is on date 2021-09-01, in_reply_to_screen_name = "swyx" and possibly_sensitive = 0

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at, is_quote_status, retweet_count, favorite_count, created_at (date)

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
1432864032235540480 swyx 33521530 2021-09-01T00:33:01+00:00 One of Java's advantages over C++ is automatic garbage collection, whereas one of Go's advantages over Java is its native CSP model. At a 50,000 ft view you can see languages as advancing by the number of hard problems that are elegantly solved by convention or language feature. https://twitter.com/swyx/status/1432864032235540480/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 279] 1432864028842356736 33521530 swyx       0 4 17 0 0 0 en  
1432864036241088513 swyx 33521530 2021-09-01T00:33:02+00:00 At the same time, infrastructure engineers increasingly embracing higher and higher abstractions to solve their problems. The DevOps movement is not so much "Devs doing Ops" as it is Ops doing Dev. As platforms develop, we are learning the chores that can be cleanly delegated. https://twitter.com/swyx/status/1432864036241088513/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 277] 1432864032235540480 33521530 swyx       0 2 7 0 0 0 en  
1432864040624091138 swyx 33521530 2021-09-01T00:33:03+00:00 To paraphrase: DX advances by extending the number of important problems our code handles without thinking of them. If we can isolate these chores, we can design them into the language, or build it into the platform. The holy grail: Language-AS-platform, Infra-FROM-code. https://twitter.com/swyx/status/1432864040624091138/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 274] 1432864036241088513 33521530 swyx       0 1 12 0 0 0 en  
1432864045133008899 swyx 33521530 2021-09-01T00:33:04+00:00 "Are you ignoring Heroku?" Heroku was so right so early - and then stagnated. We can do a lot more at build time, and at runtime. Among the platforms innovating on this: @begin, @vercel, @netlify, @PulumiCorp, @goserverless, @WaspLang! There's a tangible movement building. https://twitter.com/swyx/status/1432864045133008899/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 278] 1432864042343813120 33521530 swyx       0 2 9 0 0 0 en  
1432864048677154818 swyx 33521530 2021-09-01T00:33:05+00:00 This was part of my @Temporalio pitch: https://twitter.com/swyx/status/1417165270641045505 Because you can dynamically use retries, timeouts, task queues and timers *without any setup* and Temporal takes care of it behind the scenes: this unlocks *self-provisioning asynchrony* in your app code. https://twitter.com/swyx/status/1432864048677154818/photo/1   1417165270641045505 1417165270641045505   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 268] 1432864045133008899 33521530 swyx       1 0 7 0 0 0 en  
1432864050895994890 swyx 33521530 2021-09-01T00:33:05+00:00 I previously wrote about Cloud Distros, my term for the "second layer" of clouds forming atop the Big Three: https://twitter.com/swyx/status/1252699745883062272 Self Provisioning Runtimes are one step further into the breach - instead of YAML config and SDK code, these platforms *read the app code*.   1252699745883062272 1252699745883062272   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 273] 1432864048677154818 33521530 swyx       1 1 12 0 0 0 en  
1432935977970925571 swyx 33521530 2021-09-01T05:18:54+00:00 Today's clip: looking behind @TimescaleDB! https://share.transistor.fm/s/b8d8684b       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 67] 1432797787863744519 33521530 swyx       0 0 1 0 0 0 en  
1433107396839100420 swyx 33521530 2021-09-01T16:40:03+00:00 this was the post: https://twitter.com/swyx/status/1432864028842356736?s=21   1432864028842356736 1432864028842356736   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 42] 1432602694758273025 33521530 swyx       1 0 2 0 0 0 en  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [tweets] (
   [id] INTEGER PRIMARY KEY,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [full_text] TEXT,
   [retweeted_status] INTEGER,
   [quoted_status] INTEGER,
   [place] TEXT REFERENCES [places]([id]),
   [source] TEXT REFERENCES [sources]([id]), [truncated] INTEGER, [display_text_range] TEXT, [in_reply_to_status_id] INTEGER, [in_reply_to_user_id] INTEGER, [in_reply_to_screen_name] TEXT, [geo] TEXT, [coordinates] TEXT, [contributors] TEXT, [is_quote_status] INTEGER, [retweet_count] INTEGER, [favorite_count] INTEGER, [favorited] INTEGER, [retweeted] INTEGER, [possibly_sensitive] INTEGER, [lang] TEXT, [scopes] TEXT,
   FOREIGN KEY([retweeted_status]) REFERENCES [tweets]([id]),
   FOREIGN KEY([quoted_status]) REFERENCES [tweets]([id])
);
CREATE INDEX [idx_tweets_source]
    ON [tweets] ([source]);