Development

[WINOFFRG]

This will contain all the changelogs, decissions, discussions that I have regarding the architecture of this project.

[WINOFFRG]

After migrating from store like Zustand to Context which is just to prevent the prop drilling but not additionally being used as a store, In current migration version the store contains the ref of player and playback. Initially it was planned that why would we need to re-render the children all like that, few things were unclear at that time howsoever. But later realisation of the fact that this isn't any sort of loss but rather we would ultimately need to re-render those as data would be updated. Currently not thinking much about re-renders I will go with states in store with the pattern

const { player, playback } = useLimeplayStore() here both player and playback would be React States!

Currently the issue I see here is: In Context despite any component being a consumer or not, any children of the provider will re-render. Yes, I discussed above that we shouldn't worry about re-renders but here we should because if any developer things to add custom components which could be heavy that might get affected? Yes that's the dev concern however coudn't we expose some sort of dynamic store hook which is compatible with all kinds of store or just let the user use his own hooks across the custom hooks?

[WINOFFRG]

Gave a thought to Zustand again 😅 It's just 3KB (Bundlephobia) player and playback however are low frequency updates as much as I can see till now 🤔 So go with Context? I guess so, Overoptimising or just thinking about re-renders which haven't yet caused any such performance issue will just divert the real development goal! Let's go with context if any such issue arises or more states start pooling in will then go with Zustand!