react-elm-components VS reactfire

Compare react-elm-components vs reactfire and see what are their differences.

reactfire

Hooks, Context Providers, and Components that make it easy to interact with Firebase. (by FirebaseExtended)
Our great sponsors
  • SonarLint - Clean code begins in your IDE with SonarLint
  • Scout APM - Less time debugging, more time building
  • SaaSHub - Software Alternatives and Reviews
react-elm-components reactfire
0 14
768 3,054
0.0% 0.7%
3.4 5.8
3 months ago 23 days ago
Elm TypeScript
BSD 3-clause "New" or "Revised" License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

react-elm-components

Posts with mentions or reviews of react-elm-components. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning react-elm-components yet.
Tracking mentions began in Dec 2020.

reactfire

Posts with mentions or reviews of reactfire. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-06-21.
  • Convex vs. Firebase
    7 projects | news.ycombinator.com | 21 Jun 2022
    I was an early developer at Firebase. I think we made Firebase so easy to use and never spoke on about the technicals that the whole software ecosystem now underestimates the complexity involved. I see various Firebase competitors asserting various "mistakes it makes" without really understanding what it delivers, which is understandable because we never marketed it like that because we spoke only about how it can help you build easier.

    The idea that n queries instead of a join is slow is not as true as you would think. Firestore supports streaming and pipelines at its core, and can reuse cache across operations. At the end of the day, the data goes over a narrow network channel. If you can saturate the channel, and don't leave any gaps, what's the performance difference if the data comes from a single query or many that are back-to-back. The data is transferred to the client either way. Both Firebase databases are pipelined, so this "many round trip" argument is not a decent argument if the client can issue the queries without waiting for responses (such as the code in this article).

    The other is consistency levels and correctness. I constantly see devs call Firebase an eventually consistent database which is wrong, its causally consistent [1], and this makes a huge difference when trying to do OLTP. The offline capabilities are built on the consistency primitives, and it's the only way it can work. So while this convex article is banging on about "End-to-End Correctness Philosophy", they miss the most important quality of correctness, and if they are not careful, will miss the required engineering, and then be unable to deliver an offline cache over real-time streams. I see this playing out with Supabase, I warned them personally before they got into YCombinator that what they were building was not causally consistent. Since then, they have had to rearchitect their real-time features after shipping them. (I have not reviewed their latest design yet so I have no idea whether they have it right yet).

    Many things sucked about Firebase. The bespoke security rules and the lack of views. So Convex is on the money shipping functions on the backend. I think Supabase is shipping competitors' mistakes with row-level security language. Personally, I think Firebase's mistakes can be fixed with the addition of an open-source Firebase server [1], as the clients are already open source and the mistakes are all to do with just the server. The real tech was always in the clients anyway (offline cache, connection management, operation queues).

    It will be interesting to see if building expressly for React is a good idea. Firebase shipped many adapters, like https://github.com/FirebaseExtended/reactfire, using the "thin-waist" principle of not over-fitting. But Javascript technology moved from callbacks to async while Firebase was in the field, so the current API is not now idiomatic. But convex is setting itself for even more ecosystem fragility, what if React changes API or falls out of favor? This is a big risk! I hope they can roll with whatever happens!

    [1] https://observablehq.com/@tomlarkworthy/redis-backend-1

  • Do you have to use an ODM for firestore?
    2 projects | reddit.com/r/Firebase | 25 May 2022
    Since you mentioned you're also using React, we have a React specific library (ReactFire) that also helps out quite a bit.
  • Get current user firestore database
    1 project | reddit.com/r/Firebase | 23 May 2022
    Use ReactFire! It's our official library for React and Firebase. It has a bunch of useful hooks that probably handle most of the actions you are looking to do.
  • Intro To ReactFire v4 - Login, Logout Create Account And Protected Routes
    2 projects | dev.to | 1 Mar 2022
    From the ReactFire Example Code, see this is in AppAuthWrapper.tsx. The AuthWrapper code is from the reactfire repo to account for the removal of AuthCheck component
    2 projects | dev.to | 1 Mar 2022
    This is a quick walkthrough of a code example using ReactFire v4 in an application. The application supports login, logout, create an account, and protected routes. We also walk through two approaches for protecting routes since the AuthCheck component that existed in v3 no longer exists in v4 of ReactFire.
  • Is state management (React Context, Redux) really needed for Firebase?
    1 project | reddit.com/r/Firebase | 31 Jan 2022
    FWIW check out ReactFire, it gives you hooks and context for Firebase. Will likely feel more natural than using the vanilla platform-agnostic SDK.
  • React Query + Firestore = ❤️
    1 project | reddit.com/r/Firebase | 5 Sep 2021
    3 projects | reddit.com/r/reactnative | 5 Sep 2021
    reactfire
  • Share state using custom hooks
    1 project | reddit.com/r/Firebase | 17 Aug 2021
    - [email protected] (firebase hooks)
  • Firestore or MongoDB Atlas?
    1 project | reddit.com/r/webdev | 16 Jul 2021
    I'd say go for firebase, if you want ease of development i'd say firebase, also check out ReactFire as it allows you to integrate firebase in an easy way with react, and it also gives you a bunch of react hooks. And of course for making native apps, firebase has apks/libraries for that.

What are some alternatives?

When comparing react-elm-components and reactfire you can also consider the following projects:

react-query-firebase - React Query hooks for managing asynchronous operations with Firebase. Supports Authentication, Analytics, Firestore & Realtime Database.

use-pagination-firestore - 🔥 React hook for non-cumulative pagination of Firebase Firestore collections

strapi-connector-firestore - Strapi database connector for Firestore database on Google Cloud Platform.

rowy - Rowy is an open-source low-code platform for your backend. Airtable-like UI for your database meets cloud functions workflows, all in your browser ⚡️✨ Code in JS/TS, use any NPM, API.

Redux Slim Async - :alien: A Redux middleware to ease the pain of tracking the status of an async action

react-localstorage - Simple componentized localstorage implementation for Facebook's React.

react-famous - React bridge to Famo.us

react-children-utilities - Extended utils for ⚛️ React.Children data structure that adds recursive filter, map and more methods to iterate nested children.

firebase-js-sdk - Firebase Javascript SDK

react-swf - Shockwave Flash Player component for React

geofirex - :globe_with_meridians: :round_pushpin: Geolocation Queries with Firestore & RxJS

hooks - A high-quality & reliable React Hooks library.