jorroll

6 ms·

1. 1.▲
   by jorroll 1y ago

   I'll admit that hearing that "laziness" was something being explored for Solid 2.0 also made me uneasy. Like the OP, in my case I know it's because I'm worried that it will complicate working with Solid state in the
2. 2.▲
   by jorroll 3y ago

   The docs indicate[1] that electric's syncing logic, "shapes", are handled transactionally. How would electric handle an initial sync of 500mb or an initial sync of 10gb? [1]: https://electric-sql.com/docs&#
3. 3.▲
   by jorroll 5y ago

   Unfortunately, you cannot use React code inside Solidjs[1] so you cannot make use of the huge ecosystem of react UI components/libraries. It isn't compatible in that sense. However, there is an "official" option[2] for i
4. 4.▲
   by jorroll 5y ago

   Interesting. I guess it just boils down to different preferences.
5. 5.▲
   by jorroll 5y ago

   I think a challenge for new javascript libraries/frameworks is that, for many developers (including myself), we're evaluating the whole architecture. The question isn't, "Which library has the best API and is most perfor
6. 6.▲
   by jorroll 5y ago

   Like the author of this post, I appreciate Solid's API because component's only render (i.e. run) once by default and then you define which sections of the component should re-render on changes by using "signals" provide