2

Next.js is a piece of shit framework, (Like React is next level shit), which enforces things in the name of "convention" and is just a PITA to work with. Have to migrate an existing project to next? Make sure you use css-in-js, or you cant use next. Want to use a shared layout? lol, gtfo. Want statically optimized assets? make sure you call the correct apis in pages or you get no optimization.

┻━┻︵ \(°□°)/ ︵ ┻━┻

Comments
  • 1
    First thing next.js is not enforcing you to use css-in-js. There is a way to use shared layouts. If you haven’t heard about factory functions don’t blame next js for it. And to optimise the assets the best thing will be using CDN not storing in public directory.
  • 0
    What’s a PITA? mmmmmm piiiiiitaaaaa
  • 0
    Try SSG, hydration with Apollo 😂. And of course, try to animate page transitions.
  • 1
    @qbalsdon Pain In The Ass
  • 1
    @piperguy, oh yeah? Show me a proper way to use just css in react components and pages without all the brittle webpack overrides. Factory functions you say? Yeah right, that's the cesspool created by react. Try using dynamic layouts depending on URLs. (read: React-Router outlets) And, oh yeah CDN? try using ISR in combination with that
Add Comment