• Home
  • Blog
  • Projects
  • Bookshelf
  • About
← Back to all status updates

Link: Next.js Is Infuriating

Published 📅: ....
Last modified 📝: ....
Location 📍: Somewhere over the Atlantic between Edinburgh Scotland and Boston MA

Share this status update on BlueskySee discussion on Bluesky


👉 Next.js Is Infuriating 👈

I feel like I don't need to add much else to this topic - I used to enjoy using Next.js for a lot of things but have since pulled back and have been really enjoying Waku.

We (ab)used the same headers trick that the author shares in the above post while at Wayfair to share request context between our custom server and our RSC entrypoints, see also demonstrating it!

this repo

Tags:

micropostLinks

Loading...

Related Posts

micropost

Quick-Tip: Codex Chief of Staff Thread

Published: ....

Tip: Secrets for Cloudflare Workers

Published: ....

Tip: GitHub Created Date Filtering

Published: ....

Dependabot Hell

Published: ....

Link: What the hell is going on right now?

Published: ....

Recipe: Horchata Protein Latte

Published: ....

Zombie Retros

Published: ....

Link: How I build software quickly

Published: ....

Vacation (and streaks)

Published: ....

Polish is Important

Published: ....

<Blank> Driven Development

Published: ....

All Documentation Should Be Dated

Published: ....

Adding Microposts

Published: ....

Service Monitors and Observability

Published: ....

Leveraging service monitors properly to improve service observability.

Being Unopinionated

Published: ....

It's fine for a library to express some opinions about how it should be adopted and how the overall workflow/application in which it is adopted should function. However, it's false advertising to say that it is unopinionated.

Stop Snacking

Published: ....

No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).

No Process is Invisible Process

Published: ....

Low/no process workflow wasn't actually no process, it was only an "invisible" process. An implicit contract with everyone on the team to do that async workflow on their own time.

Links

Link: What the hell is going on right now?

Published: ....

Link: How I build software quickly

Published: ....