Recommending Hooks API before it is has been accepted in React

[paultannenbaum]

First off, thank you for the great library.

I realize that @acdlite is a core dev on the react team, but Is it smart to announce no future maintenance and recommending hooks when the feature is still a proposal and has not been accepted into the core react library? Would also love to see some examples on how you believe the new hooks api solves the same problems, as I personally am still not seeing the api to be as powerful as the composability of a library like recompose.

[istarkov]

Have u read this https://reactjs.org/docs/hooks-custom.html ?

[istarkov]

You will have much more freedom with hooks

[paultannenbaum]

I had not, you are right this could help a lot.

Isn't this still just a proposal? Which means it may not be added to React core.

[sorahn]

I think it's coming no matter what, but the names / implementation might change slightly.

Facebook said they've been using it in prod for a month already.

[gaearon]

Nothing is changing in practice. Andrew’s wording was too strong but he didn’t mean the library would suddenly become unsupported.

Your code will continue to work, and new versions for newer React updates will continue to be released. And Andrew hasn’t personally been working on Recompose for two years so that hasn’t changed either.

See my reply in #756 (comment).

[paultannenbaum]

Thanks @gaearon. I am going to close this issue as #756 seems to be discussing the same thing.