Hacker News new | past | comments | ask | show | jobs | submit login

It's interesting that the React Router team, which is building the competing Remix framework (similar to Next but based on React Router) is arguing that instead of supporting static page generation, they will just urge their users to use CDNs with aggressive caching rules.



I'd imagine the hard part with that approach would be cache invalidation. I'm curious to see how they try and address it.


You could use webhooks on deploy to call your CDN's API to purge the cache. Otherwise, I guess just keep it time-based.


This instinctively makes more sense to me.

Still, good to have options. It will be interesting to see how Remix is received once it launches. Next is currently peerless for DX-friendly React frameworks.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: