he/him 
"Syntax" errors 
pic.twitter.com/BFQuG7I4cm
Show this thread
-
Looks cool. Hot take: any object with a type property will most likely benefit from being converted to an explicit class instance.
Not really. These are constantly crossing an IPC boundary, having to manually construct these class instances would be pointless. There's literally no other metadata or functions besides those properties, why shouldn't it be an object?
-
-
- Type safety and property validation. (Although I assume you're using TS or Flow?) - Not having to repeat property names, just pass the values into the constructor. - To avoid the type property, which serves a different purpose than the other, type-dependent properties.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
As for IPC: doesn't mean you can't marshall using a toJSON method. I realize it's a matter of opinion though. Personally, I just feel like type properties in particular reinvent the wheel.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.