uPlot VS zustand

Here is a very efficient 2D canvas lib that is extremely efficient https://github.com/leeoniya/uPlot i recommend looking through their readme and seeing if it solves your current problems.

BACKEND:

It's about 3000 lines of Crystal code https://crystal-lang.org/ -- it's been an absolute dream to program in. Ruby-like syntax, statically compiled performance. Nice standard library. Would recommend :)

Performance == caching

Local ephemeral filesystem for shortest-term caching.

Redis for shared medium-term caching and locking.

S3-compatible object storage for longest-term caching (for raw data feeds pulled every evening by a cronjob).

FRONTEND:

Bootstrap

uPlot https://github.com/leeoniya/uPlot

Just a sprinkle of inline JS+CSS on the page.

you can use matchMedia to detect devicePixelRatio changes and re-sync:

https://github.com/leeoniya/uPlot/blob/190134aa844cfa2a0c052...

everything stays crisp even as you browser-zoom. e.g. https://leeoniya.github.io/uPlot/demos/area-fill.html

Safari's slow release cadence (typically tied to OS version upgrades) does leave it more broken and for longer than Firefox, Chrome, Opera and other browsers that are updated more frequently and not tied to the OS.

just recently i ran into incompatibilities with Safari < 14 needing the old-spec matchmedia api:

https://github.com/leeoniya/uPlot/issues/538#issuecomment-87...

uPlot will handle this. https://github.com/leeoniya/uPlot

If you are showing 100s of thousands of points, I'd still go with canvas eg uPlot. It's a really, really excellent library.

The existing node red chart tools is not great. I'd like to be able to use uplot instead. The uplot-charts node should work very much like that charts node built into node-red-dashboard.

super cool!

i've done my share of optimizations and benchmarking charting libs [1] but this goes deeper still.

SVG is not a good choice for large raw datasets when you need performance.

[1] https://github.com/leeoniya/uPlot#performance

Daishi Kato, creator of Zustand and Jotai, says there are a few things we need to support RSC serialization:

Zustand

Link: https://zustand-demo.pmnd.rs/

For more code examples visit the documentation here

Have you ever wanted to learn state-management but it felt so overwhelming to get started with Redux? Or maybe you're already using Redux but don't want to take the burden anymore? If so, you might want to take a shot at Zustand! Its an amazing state management library that's easy to get started and maintain in a long run. In this post, we'll dive into creating & sharing stores with this tiny Redux alternative.

You add the current user state to a React Context or state management library, read from it on the top bar, and write to it after a user signs in. Done. No big deal, right?

Zustand

I tried using skipHydration inside my zustand store based on their docs, then rehydrating it inside my modal. So far im getting the same errors. https://github.com/pmndrs/zustand/blob/main/docs/integrations/persisting-store-data.md

Reducer-based: requires dispatching actions to update a big centralised state, often called a “single source of truth”. In this group, we have Redux and Zustand.