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
1436712591292829697,33521530,2021-09-11T15:25:49+00:00,"Since @QwikDev serializes all its state onto HTML, the question arises what to do with unserializable state.

Chanced upon Dan’s comment today:
“This is what doomed ASP .NET WebForms, and we'd like to learn from their mistakes rather than repeat them.”

https://github.com/reactjs/rfcs/pull/188#issuecomment-824139957 https://twitter.com/swyx/status/1436712591292829697/photo/1",,,,95f3aaaddaa45937ac94765e0ddb68ba2be92d20,0,"[0, 277]",1435223333398843397,33521530,swyx,,,,0,0,4,0,0,0,en,
1436776365823598595,33521530,2021-09-11T19:39:14+00:00,"Lighthouse is great but the fact that you can get such wildly different results on the exact same site is just actively counterproductive.

The default experience has you “holding it wrong” and none of the impt info is in the screenshot. Dear @ChromeDevTools, you CAN fix this. https://twitter.com/swyx/status/1436776365823598595/photo/1",,,,95f3aaaddaa45937ac94765e0ddb68ba2be92d20,0,"[0, 277]",1436733804174008321,33521530,swyx,,,,0,1,38,0,0,0,en,