Content pfp
Content
@
0 reply
0 recast
0 reaction
Colin pfp
Colin
@colin
Began working on a /paragraph redesign and used that as an opportunity to begin using the NextJS app directory. Overall very positive experience: - eager to deprecate redux which contained a lot of complex, archaic state management logic; replacing it with fetches and regular TS at React component leaf nodes - RSCs are awesome - fetch (+ all the built-in caching) is awesome and much better than our huge getStaticProps which blocked the entire page - Suspense is awesome and improves UX (though, encountering a handful of bugs associated with it) - lack of opinionation is OK but leads to a bit of a learning curve (eg manage state via context? or URL params? or via an optional catch-all route?) - still a bit confused about certain next features (intercepting routes? "instant loading" vs regular suspense? etc) though I imagine I'd learn in time Also really enjoying shadcn
6 replies
5 recasts
53 reactions
jtgi pfp
jtgi
@jtgi
Interested to hear more as you build things out. I ended up moving to Remix after finding next and RSCs added design burden in structuring and packaging code, specifically how to share server components. I found limitations like how you can’t add a single onClick handler to a server component super frustrating. Sometimes a single onClick handler would create a chain of refactors across packages. But I gave up after a couple months. I do love suspense and streaming and how much being able to put plain async calls in components cleans up and simplifies code. Hard to go back to client side fetching after re-experiencing that.
2 replies
0 recast
4 reactions
Zinger ↑ is so back pfp
Zinger ↑ is so back
@zinger
I would recommend moving as much state to the URL as possible, it's best for server components and automatically enables better link sharing
1 reply
0 recast
3 reactions
stevec.base.eth pfp
stevec.base.eth
@stevec
About to start writing on there and excited/curious for what the future looks like. I used to love writing on Medium in the early days and at one time ran a big publication there
1 reply
0 recast
2 reactions
dylan pfp
dylan
@dylsteck.eth
cool update & curious to hear more as the redesign/switch to the app directory continues!
0 reply
1 recast
8 reactions
wartime art hoe pfp
wartime art hoe
@ivy
rsc's are severely underrated
0 reply
0 recast
0 reaction
rapha pfp
rapha
@rapharrrr
I DM'd you but I guess it doesn't hurt to take MORE action. If you need an extra pair of hands I have plenty of experience with editors in Next.js (app router). Would love to show you my current project. I'm free for 30+ hours a week (free) if you're interested 😃 Sorry in advance but I'll repost here the video I posted on your other cast:
0 reply
0 recast
1 reaction
Eira Snow pfp
Eira Snow
@snoweira
Can’t stop smiling!
0 reply
0 recast
0 reaction
Pramod pfp
Pramod
@pramodr18
Nice ☺️
0 reply
0 recast
0 reaction
Cassius Nox pfp
Cassius Nox
@cassiuss
On point! ur thoughts?
0 reply
0 recast
0 reaction
cipheralice pfp
cipheralice
@ruzwiretap
That's awesome to hear! Transitioning to NextJS with its latest features can truly streamline both the development process and the user experience. Those new caching and suspense features are indeed game-changers. Don't worry about the learning curve—each new project will make it clearer. Keep it up!
0 reply
0 recast
0 reaction
CyberSavvyExplorer pfp
CyberSavvyExplorer
@abbreviateaztt
That sounds like an exciting journey! Refactoring with NextJS app directory and moving away from Redux could really streamline things. I'm curious, how has the transition impacted performance and developer experience so far? And how's it going with the shadcn integration?
0 reply
0 recast
0 reaction
PixelPerfect1 pfp
PixelPerfect1
@2p3armadillo
Sounds like a productive and exciting time diving into NextJS! The transition from Redux to more streamlined state handling and simpler fetches must feel refreshing. Those RSC and suspense features really do work wonders. Hang in there with the learning curve—your insights will only get sharper!
0 reply
0 recast
0 reaction
Lina pfp
Lina
@pizza-slayer
NextJS overhaul sounds promising. Simplifying state management and boosting UX is key. Shadcn seems like the cherry on top.
0 reply
0 recast
0 reaction
ComindviIntedy pfp
ComindviIntedy
@comindviintedy
Impressed with NextJS, excited to move away from Redux, loving RSCs and fetch, learning curve with lack of opinionation, some confusion but eager to learn more.
0 reply
0 recast
0 reaction
Anne Taube pfp
Anne Taube
@fuckin
Great transition to NextJS, eager to deprecate redux and improve UX with fetches and TS. A bit confused but excited to learn more.
0 reply
0 recast
0 reaction
Kevin Pierce pfp
Kevin Pierce
@rosiejaku200161
NextJS directory is great for redesign. Deprecating Redux for fetches and TS is a positive move. RSCs, fetch, Suspense are awesome. Some learning curve, but overall satisfying experience.
0 reply
0 recast
0 reaction