Earlier quoted context omitted.
Thanks for creating Firebase! It's really the definition of an managed database/datastore. Do you see InstantDB as a drop in replacement ? To be honest I don't want to have to worry about my backend. I want a place to effectively drop JSON docs and retract them later. This is more than enough for a hobbyist project, though I imagine at scale things get might not work as well.
If you only need simple dropping and collecting back, maybe you should consider about AWS S3 or Supabase storage.
Show HN: InstantDB – A Modern Firebase
81–90 of 308 posts
Re: Show HN: InstantDB – A Modern Firebase
#82Sounds conceptually similar to Zero: https://zerosync.dev/ I haven't looked in detail yet — what are the main differences relative to Zero?
From that blog: > We are working toward a source release in summer 2024 and an open beta EOY 2024.
Re: Show HN: InstantDB – A Modern Firebase
#83Do you have clients for Android, iOS, Mac apps, Flutter, Rust? If not, how hard do you think it is to implement a client for an additional language?
The core client SDK is pretty small -- it's about 10K LOC. We want to get the core abstractions right in JS-based environments, than expand. We really like Mitchel Hashimoto's post about how he built Ghostty on different platforms [1] [1] https://mitchellh.com/writing/zig-and-swiftui
Re: Show HN: InstantDB – A Modern Firebase
#84Earlier quoted context omitted.
Co-founder of PowerSync here. Would love to hear what you would like to see improved in PowerSync :) Thanks!
The docs for React Native. I had to piece together how to do stuff from the code examples and a YouTube video tutorial because they're pretty sparse with information, and missing a cohesive tutorial that could get me setup with CRUD locally. Plus the initial setup process from the npm page, which itself was notable for how much was required. I haven't attempted to setup the backend yet, so that's my feedback so far.
Re: Show HN: InstantDB – A Modern Firebase
#85Sounds conceptually similar to Zero: https://zerosync.dev/ I haven't looked in detail yet — what are the main differences relative to Zero?
I think it would be difficult to compare at this point, as there aren't many details about Zero outside of the blog on their landing page. I believe it's very much in early (but active) development. From that blog: > We are working toward a source release in summer 2024 and an open beta EOY 2024.
Re: Show HN: InstantDB – A Modern Firebase
#86Re: Show HN: InstantDB – A Modern Firebase
#87Re: Show HN: InstantDB – A Modern Firebase
#88Side note: Electric SQL is currently going through a rewrite, so things are a bit up in the air.
Re: Show HN: InstantDB – A Modern Firebase
#89Their icon looks like fig.io but inverted
Re: Show HN: InstantDB – A Modern Firebase
#90What's the short summary of how the authorization system works for this? One of the things I find quite nice about firebase is the quite powerful separation between the logic of data retrieval / update and the enforcement of access policy -- if you understand it you can build the prototype on a happy path with barely any authorization enforcement and then add it later and have quite complete confidence that you aren'…
> What's the short summary of how the authorization system works for this? We built a permission system on top of Google's CEL [1]. Every object returned in a query is filtered by a 'view' rule. Similarly, every modification of an object goes through a 'create/update/delete' rule. The docs: https://www.instantdb.com/docs/permissions The experience is similar to Firebase in three ways: 1. Both languages are based on C…