CSFrequency / react-firebase-hooks

React Hooks for Firebase.
Apache License 2.0
3.56k stars 304 forks source link

Is this still actively maintained? #93

Closed cd-a closed 3 years ago

cd-a commented 3 years ago

No activity for half a year, and given that the PR for firebase 8 isn't even touched makes this project not usable for the current iteration.

Are the maintainers still here?

Satyam commented 3 years ago

The original author is obviously falling behind his GitHub notifications, and hasn't made any commit to any of his projects for a while. He lists several accounts: https://twitter.com/chrisjbianca and https://www.linkedin.com/in/chrisbianca on his page: https://csfrequency.com/about-us/. I don't have accounts on any of these services, could someone ping him and let us know?

If he is busy at the moment, waiting for him to be available would be a better option than forking the project and registering a new package on Npm.

If he is somehow unable to work on this, enabling someone to help would be better.

Otherwise, forking it would be the only option, the soonest we know the better.

A wild thought: would the Firebase team at Google be willing to take this up?

cd-a commented 3 years ago

If he is busy at the moment, waiting for him to be available would be a better option than forking the project and registering a new package on Npm.

I agree.

A wild thought: would the Firebase team at Google be willing to take this up?

As I see it, there's https://github.com/FirebaseExtended/reactfire which states in the status:

This repository is maintained by Googlers but is not a supported Firebase product. Issues here are answered by maintainers and other community members on GitHub on a best-effort basis.

Satyam commented 3 years ago

@dahmc As I found out, Google lists a lot of Open Source projects related to Firebase, including this very same one: https://firebaseopensource.com/projects/csfrequency/react-firebase-hooks/ So, my suggestion about them taking it over was pointless, as there are projects for Angular, Vue and what not so, why would they bother about this one. So forget about my last suggestion.

Reactfire looks attractive, it has twice as many stars in GitHub, though it has just a sixth of the weekly downloads.

The number of warnings about being experimental (or perhaps has some experimental features) and the warning you quote are clear downers.

Most of the package is made of wrappers around rxfire which adds a lot to its weight in all senses: download size, processing, memory, etc. Most of its features depend on what rxfire can do.

I still prefer this package, unless it is definitively proved dead in the water.

cd-a commented 3 years ago

Yes, I agree completely, this whole RXJS/RXFire dependency seems very overengineered. You can tell it's coming from AngularFire which depends heavily on RXJS anyway.

The simplicity of this package is definitely what attracts me more as well. It's a more react style of doing things.

If there's no sign of life in the near future, we could just agree on a fork and go from there.

cd-a commented 3 years ago

Looks like @chrisbianca is back and has been busy merging lots of PRs, which is great news. Thanks for taking care of that, Chris.

We should see a new release soon then, I hope. So I am happy to close this one.