Frontend

My thoughts after several weeks of working with NextJS 14 / app dir / RSCs:

- bit of a learning curve (lots of stuff happens behind the scenes, eg there are various levels of caching on Vercel by default) 
- Jotai is much cleaner and easier than Redux
- deduped fetching in RSCs is awesome and much better than getStaticProps
- Suspense and loading states are great and make the app feel much more responsive
- Lots more files, since we now need to separate client & server components on a per-file basis (and use folder-based routing)
- Intercepting / parallel routes are neat

Overall, I'm a big fan and it seems like a large improvement over the previous paradigm

You might also like Zustand (same crew at Jotai), a bit more similar to Redux vs. the atomic state model of Jotai (which models Meta's Recoil)

cma.xyz. Founder /paragraph, ceo /mirror, previously at Google & Coinbase 

/new-york by day 🗽 /latenightcrew by night :) Fan of eating tacos and bringing people together, often at the same time 🌮 oh and /untzuntz 😈

Looked into it and my understanding was that zustand is meant more for global state vs jotai was moreso to avoid prop drilling.

No more need for global state in the paragraph codebase since we now just fetch data everywhere, so jotai seemed like a better fit to share smaller amounts of data to child components

You might also like Zustand (same crew at Jotai), a bit more similar to Redux vs. the atomic state model of Jotai (which models Meta's Recoil)

https://docs.pmnd.rs/zustand/getting-started/comparison

https://jotai.org/docs/basics/comparison

I haven’t quite wrapped my head around server actions yet. I think our usecase isn’t the most compelling because we already have a fully fledged API outside of nextjs, so it seems like we wouldn’t reap much benefit from server actions.

Cc @sourav who was also exploring this earlier today

Nice write up. I agree it’s an improvement and harder to grok. 

Server actions are also a nice DX improvement (automatic serialization and routing) for certain use cases. I wish one could invalidate/refresh an individual server component!