[HN Gopher] My take on the current React and Server Components c...
___________________________________________________________________
My take on the current React and Server Components controversy
Author : hyperknot
Score : 17 points
Date : 2023-07-05 21:34 UTC (1 hours ago)
(HTM) web link (phryneas.de)
(TXT) w3m dump (phryneas.de)
| drb999 wrote:
| Reading this makes me think I guessed the right way going "all-
| in" on Remix vs Next. It was a guess, but it's just so much more
| intuitive and web standards friendly, serverless friendly,
| browser friendly...
| crooked-v wrote:
| RSC feel like a poorly-documented 0.5 beta filled with endless
| breaking changes being pushed as default for some inexplicable
| reason.
| thinkingkong wrote:
| The teams working on Next and React are pushing things a little
| too fast. The problem is the bulk of the consequences of their
| actions fall on library developers and maintainers. Frankly Im
| not even sure why everyone is in such a rush to rewrite all the
| docs, components, libraries, and frameworks for the unpteenth
| time.
| nathanaldensr wrote:
| Boredom alleviation and paycheck justification.
| rjbwork wrote:
| Fire and Motion.
| ChrisLTD wrote:
| I don't believe Server Components are a make-work scheme for
| React specialists, but they feel like a make-work scheme for
| React specialists.
| mmmeff wrote:
| I had a junior on my team propose we switch our year old project
| to Next's app router.
|
| After telling him no, I became concerned that I was becoming all
| the lead developers I've worked with in the past that shut me
| down and, at the time, seemed to be holding back innovation on
| our team.
|
| I get it now. I totally get it.
___________________________________________________________________
(page generated 2023-07-05 23:00 UTC)