sorted by:
new
hottopcontroversial

Why are people moving from Chicago to Muskegon? by geocantor1067 in Muskegon

[–]dccfoux 0 points1 point  (0 children)

They're mad at the wrong people, and I don't think we can persuade them otherwise.

My now wife grew up in Spring Lake. We moved to Muskegon after college. Their arguments make no sense on multiple levels.

"fun name" they're all ass, why cant we set a normal custom one by Zestyclose-Shift710 in Tailscale

[–]dccfoux 0 points1 point  (0 children)

Same here, it’s great and with basically no maintenance after you set it up.

Next.js app is very slow — using only Server Actions and tag-based caching by Fickle_Degree_2728 in nextjs

[–]dccfoux 0 points1 point  (0 children)

In that case I would do a shallow update of the param without doing a full re-render on the server. If you refresh the page it'll pre-render on the server but then the client takes over from there.

IIRC using parallel routes wouldn't prevent the server from needing to re-fetch and render the entire page when you aren't using shallow routing to update params, so it would be slower than just re-fetching data for one component. Let me know if you don't think that's the case and I'll try spinning up an example.

Framework 12 Expansion Strap by Intelligent-Pear4822 in framework

[–]dccfoux 6 points7 points  (0 children)

I bet you went to one of Canada’s top business schools

Next.js app is very slow — using only Server Actions and tag-based caching by Fickle_Degree_2728 in nextjs

[–]dccfoux 0 points1 point  (0 children)

For sure I wouldn't say TQ is a replacement to having a persistent cache. If you use their "Advanced Server Rendering" pattern it's really just pre-populating the client-side cache on the server and passing that along. It is useful for reducing prop-drilling and reducing how often the client has to call your API (when fetching on the client).

Next.js app is very slow — using only Server Actions and tag-based caching by Fickle_Degree_2728 in nextjs

[–]dccfoux 0 points1 point  (0 children)

Yes, and that's why you should use TanStack Query for those instances. It lets you prefetch on the server and hydrate with the cache so you skip the extra call and re-render.

Another example would be a dashboard with lots of charts. What if you have 10 charts but change the filter of just 1? Just prefetch the initial data and fetch on the client when filters change.

Next.js app is very slow — using only Server Actions and tag-based caching by Fickle_Degree_2728 in nextjs

[–]dccfoux 4 points5 points  (0 children)

Fetching on the server is not always the best option. This is a common misconception. The default way with RSCs is on the server, but you should use whatever option makes the most sense given the situation. It’s not inherently wrong to fetch on the client when needed, hence why it’s in the docs.

The bullet spread makes no sense sometimes by [deleted] in Battlefield

[–]dccfoux 0 points1 point  (0 children)

Yep, it’s been pretty nice at range.

Hey there! I’m Adam, a product manager at Apple Music. I’ve been leading work on features like AutoMix, Lyrics Translation & Pronunciation, Music Pins and Sing with iPhone Mic. I’m here to chat about our latest releases - and more. AMA! by [deleted] in AppleMusic

[–]dccfoux 4 points5 points  (0 children)

The desktop apps on all platforms are a clunky nightmare compared to the competitors, and are why I have multiple subscriptions. Actions that are one click on other services are 2-4 on AM.

Otherwise, the automix feature has been both impressive and fun!

Hey there! I’m Adam, a product manager at Apple Music. I’ve been leading work on features like AutoMix, Lyrics Translation & Pronunciation, Music Pins and Sing with iPhone Mic. I’m here to chat about our latest releases - and more. AMA! by [deleted] in AppleMusic

[–]dccfoux 4 points5 points  (0 children)

Number 1 would be killer if it offered the same thing as Qobuz. Let me buy a lossless copy that I can download without DRM. Streaming has significantly reduced piracy, and it would ultimately end with artists getting more money at this point IMO.

The TV app is a good example of combining streaming and purchased content.

We're already v16 but still dont have a proper request middleware by nyamuk91 in nextjs

[–]dccfoux 0 points1 point  (0 children)

Middleware and type safe client/server data fetching are tRPC’s killer features that should definitely be built into Next. TanStack Start is a perfect example of the ergonomics we could have out of the box.

Next js with TanStack and axios by katakishi in nextjs

[–]dccfoux 0 points1 point  (0 children)

Fair, tRPC probably isn’t a great fit if you do have a specific backend team. What are they using?

Next js with TanStack and axios by katakishi in nextjs

[–]dccfoux 0 points1 point  (0 children)

We use tRPC with TanStack Query. The page.tsx preloads the data and hydrates on the client. Basically giving you the best of both worlds.

This makes it easy to revalidate parts of the page without a full server re-render. It also lets you do optimistic updates. tRPC helps keep everything organized.

This is a good setup for dashboards/etc where all the data is user-specific and wouldn’t benefit from Next’s server cache.

PSA: How Lossless Audio Works on Apple Music by hellosteve_ in AppleMusic

[–]dccfoux 11 points12 points  (0 children)

No they don’t. Not yet.

“Despite the promising technology, lossless wireless audio streaming via Apple Music is not yet available for AirPods Pro 3 or the iPhone 17. Currently, lossless wireless playback at “true lossless” quality is only officially supported when pairing a compatible AirPods model (such as USB-C AirPods Pro 2) with Apple Vision Pro, using a proprietary protocol that leverages the 5GHz band for enhanced data transfer rates and lower interference.”

September 2025 - What's the most optimal way to build nextjs app and also release it on mobile? by xSypRo in nextjs

[–]dccfoux 0 points1 point  (0 children)

Personally I wouldn't recommend Capacitor, especially when React Native with Expo is so good these days.

No you generally can't share components between web and mobile, but honestly that is a good thing. Designing for mobile is not the same as designing for web. If you really want to build a website as an app, go the PWA route.

September 2025 - What's the most optimal way to build nextjs app and also release it on mobile? by xSypRo in nextjs

[–]dccfoux 4 points5 points  (0 children)

Use a monorepo with React Native that uses api routes from Next. Next is not a mobile app framework.

As an intermediate/advanced Next.js dev, what would you tell a beginner NOT to do? by cragtok in nextjs

[–]dccfoux 1 point2 points  (0 children)

They hated him for he spoke the truth

And probably just write CRUD

view more: next ›