Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Eagerly awaiting the React Native compatible version. https://zerosync.dev/ is the main alternative I'm considering.


PowerSync (https://www.powersync.com/) is also a great alternative, and my preferred choice. SDK's available for React Native, Flutter, JS, Swift, Kotlin etc


I've heard about this one as well. I'm not sure why it seems to have less "hype" than Zero or ElectricSQL. I'm going to play with it this weekend. Thanks for sharing.


Electric works with Expo / RN now.

PGlite is coming — we have a new WASI build that is the basis for native mobile support. (It’s working in dev, but still needs some more polishing and bindings).


Sorry should have mentioned that I need PGlite or SQLite support. I am very much looking forward to PGlite on Expo/RN!


As are we :) btw checkout LiveStore if you haven’t already:

https://expo.dev/blog/local-first-application-development-wi...

It’s not fully released yet but it is now open to GitHub sponsors and it’s very cool.


Oh this is very cool as well. Thank you for sharing. I hadn't heard of LiveStore.


Any thoughts on Flutter support? I believe that existed in the previous version of Electric.


What are you using for your WASI runtime?


A couple of things here:

- the WASI build is targeting WASI snapshot preview 1, and so should work in any compatible runtime.

- for the web, currently we use Emscripten, but we are considering moving to a single WASI build there as well. We'll be writing our own JS WASI shim if we do. Having full control of the JS code will help to solve some of the problems we've faced with Emscripten.

- we are also exploring a route to native where we take the WASI build and decompile it back to C. This seems a little mad, but it makes it possible to compile (with any tool chain) a native binary with a very minimal WASI-like api that can be linked to from any app. It essentially end up a little like the SQLite amalgamated header file as a build route. It's very experimental, and we haven't committed to it yet, but it looks like it may work.


This is interesting. Can you go into a bit more detail on why the WASM decompiling would be helpful as opposed to just using the native codebase?


Dynamic linking on iOS is complex, and Android also brings some toolchain complexities. It would be possible to do a native build and link it, and that is a route we are also exploring, but a single C file that can be linked with any existing toolchain would simplify things for users.

It also allows us to implement a VFS layer underneath PGlite in a native mode. So things like the in-memory VFS, or a custom VFS, would be possible.

We have not committed to one route or the other yet.


You should check out Triplit as well, we have React Native support[0] and the best Typescript integration by far

0. https://www.triplit.dev/docs/frameworks/react-native


Another one I have to play with. Thanks for sharing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: