Brian Kim

Ahhh I’m rereading this and seeing I might have misunderstood your suggestion. You’re saying we put the props in their own key on the object passed to components, so that...

Hmmmm so I thought some more and still think the current approach is the most ergonomic. There’s something really intoxicating about the idea that a component can just be a...

@monodop See https://github.com/bikeshaving/crank/issues/26#issuecomment-615930117 where I talk more about why I chose to use `this` too!

@elektronik2k5 What @ryhinchey said. There are some nice things from React that we should take, and I think the signature of function components is one of them, but many things,...

@ndp My dog passed away last year, and I really do miss going on long walks while thinking about code. I’ve gotten the feedback that code like `for await ({throttle}...

@lukejagodzinski I’m not sure aliasing the props variable is the right approach, even it does seem interesting. With JSX and createElement, we essentially have to create a copy of props...

No I think you’re definitely onto something! One cool thing is that we can actually reuse arrays of elements, because they’re preserved between renders: ```tsx function *VirtualList() { let els...

Thank you for your interest! Unfortunately, I only speak English and Korean so this is something I need help with. However, I’m very interested in having docs/essays translated to Chinese...

@Hezhong123 If you can suggest a translator I’d be eternally grateful.

@ryhinchey Reopening this issue for visibility and also actionability. It could be nice to document it in the detailed getting started stuff (there’s an open PR for detailed getting started...