👋 @ricky.fm if you have time

nice! i don’t want to contribute to the thread as I’m not really a next.js user, but seeing the possible solution being to perform static analysis to determine whether args are being used rather than encourage explicit mapping of args with linting confirms my feelings that next is too magic for me

it literally has react in the name and is presumably intended to be used within a react app oh my god

a bit too assertive for my taste

try me!

My main complaint about steam machine :(

interface when possible, types when necessary

I’ve found it only working if i spend a lot of time compiling the flashcards myself. Pre-made collections aren’t nearly as effective.

the european mind cannot comprehend this

If rolldown-vite wants to be a drop-in replacement from vite v7, and it changes css parser, isn’t it also a rolldown-vite issue?

:( Will try to extract this to a reproducible example, but would be great with a better stack trace showing the faulty css file.

aah, I see - thanks for the clarification! although I wish there was a way to globally set cancelRefetch to false.

Anyway I’m excited for it because I could introduce new code organization practices in our SPA and the day I manage to convince people of BFF being worth it it’s just flip a switch *poof* server rendered!

Shouldn’t offloading rendering from the main thread potentially come with some performance improvements? Or is the serialization a bottle neck?

With data centers I really meant entirely different cloud platforms (AWS vs GCP)

Can’t for the life of me understand how a service like statuspage doesn’t have redundant setups with automatic failover in at least 2 datacenters.

is this their vhs vs betamax moment?