TwistedMinda

@RobertSasak Hello! One year later is it still the preferred way? Because I can't get it working personally. Because I have multiple atoms that I need to have preloaded before...

@RobertSasak Yes I'm sorry I was only in the learning process, and decided finally to switch to jotai for my final choice. Don't have the codebase to reproduce the bug...

@dai-shi @israelidanny What's the state of this? If I'm correct it's been setup correctly. Just lacking some notes on Valtio integration doc, right? Too bad that the PR went through...

@dai-shi Does it need some documentation ? If I understand the usage correctly, it looks like this: ```tsx const urlAtom = atom('https://jsonplaceholder.typicode.com/posts'); const wrapperAtom = atom((get) => { const url...

@dai-shi I totally agree with your 2 points: - denoify is a bit too much for jotai - deno could improve node-compatibility for better adoption, and jotai being a fairly...

@dai-shi What's the state of React 18 concurrent mode stability and this issue in general? Should you run some tests again? Or put "on hold" for now?

@dai-shi > comparison can be in separate docs, I guess. Yeah true, not the most important indeed. > I would explain with useState analogy. I think this is a bit...

@dai-shi Okay I've added your comparison to useContext to the Comparison page. But I also noticed that the "Concept" page is just a comparison to recoil & useContext, so I...

@dai-shi Yeah sure, forgot to set it as draft, but it's totally a first step. I need help to know if I'm going on the good way. Looking forward to...

Might be related to https://github.com/software-mansion/react-native-screens/issues/1661