I work at Facebook and we have been using it in our code base for a while.

General sentiment towards hooks are positive. There are many benefits of hooks which you can find on the React website.

However, the React team emphasizes that you would be better off not rewriting your whole app with hooks for these reasons:
1. It's still experimental, APIs may change in future
2. It takes effort to rewrite your app, and the marginal benefits are questionable. Hooks are great when writing new code because they are shorter but if you have already written code in classes, you have paid the cost and rewriting it wouldn't help much.

There's one reason to rewrite though - smaller bundle size because classes (which lifecycle method names can't be transpiled) are now gone from the bundle.

I would advise you to try it out but not commit too much to it. Wait for it to be more stable and for best practices around using hooks to emerge before rewriting your whole app in it.

Where's the fsck?

But have you tested with corner cases?

FB runs on PHP (More of Hack). Instagram runs on Django.

@S-Holmes-MD Westin Stamford Hotel in Singapore

Production issue. It's a term at FB

webpack bruh

Try http://yangshun.im/commitbait

Remember that's always commit amend and force push

By using dynamic languages you are making a trade-off and all of them have this problem and it's not specific to JavaScript. Use Flow or TypeScript to save yourself the agony.

Use Jest. It has all you need

Correct me if I'm wrong, but your password when sent to the server for verification is still in plain text. Can't they compare it with the dump then? That doesn't mean your password is stored in plain text.