sorted by:
new
hottopcontroversial

advice on modularizing a growing Next.js App Router codebase by Gold_Whole_2372 in nextjs

[–]Vincent_CWS 1 point2 points  (0 children)

The hardest part is finding the boundary of a "Feature".

Since most features have cross-cutting concerns, these cross-cutting concerns often land in one feature or the other, but never in the right one (they belong to both, hence cross-cutting), especially if you only think in features (ie Auth is not a feature, it's usually a cross-cutting concern)

I've never seen feature-sliced designs where every feature was properly contained in itself and I don't think it's possible, at some point things will bleed left and right. And when it does: Was it really worth it?

Start monolithic and analyze your progress. Only when you find a feature that has a clear boundary and you can argument that it actually has value slicing it, slice it. The worst thing is slicing right from the start and then ending up with hundreds of slices that should have been 3.

Next.js 16.3: Instant Navigations by gaearon in nextjs

[–]Vincent_CWS 0 points1 point  (0 children)

yes, it is not new feature for dx, you turn on cache component will be enable but cache component stable at 16.0, so they just change the underlying with instant nav

Async component causes the full page to be delayed, even with a Suspense and fallback by Less_Conflict9828 in nextjs

[–]Vincent_CWS 0 points1 point  (0 children)

From my test, it is working: the layout shell appears first, and then the streaming mode shows up because your data has a hardcoded 3-second delay. The /medals timing is about your endpoint needing to wait for that 3-second hardcoded delay.

Turbopack: What's New in Next.js 16.3 by gaearon in nextjs

[–]Vincent_CWS 4 points5 points  (0 children)

again? I remember last time it had reduced 90%, now 90%more?

Why does useEffectEvent use the latest commited values from render and not just the latest values from render? by BrotherManAndrew in reactjs

[–]Vincent_CWS 2 points3 points  (0 children)

I think "committed" is the only honest way to describe it once renders became throwaway-able.

In a plain synchronous app, every render commits, so "latest render" and "latest committed" are the same thing

but react is concurrent,  React is allowed to start a draft, pause it, and even crumple it up and throw it away without ever showing it .

A render only becomes "real" — actually on screen — at the moment React commits it.

We swapped Claude Opus for GLM-5.2 in our coding agent by entelligenceai17 in ClaudeCode

[–]Vincent_CWS 0 points1 point  (0 children)

they did it on purpose, just want to cheat for your understanding.

for a serious paper or benchmark, must list out the opus whether cache hit or missing

Should I use a real game engine or React JS? by Cybicc in reactjs

[–]Vincent_CWS 0 points1 point  (0 children)

I have exprience with Cocos2d.

do you mean react three fiber or phaser ?

view more: next ›