My take on the current React and Server Components controversy
1–10 of 78 posts
Re: My take on the current React and Server Components controversy
#2The 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.
Re: My take on the current React and Server Components controversy
#3The 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.
Boredom alleviation and paycheck justification.
Re: My take on the current React and Server Components controversy
#4I 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.
Re: My take on the current React and Server Components controversy
#5The 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.
Fire and Motion.
Re: My take on the current React and Server Components controversy
#6The 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.
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.
Re: My take on the current React and Server Components controversy
#7Reading 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…
Re: My take on the current React and Server Components controversy
#8RSC feel like a poorly-documented 0.5 beta filled with endless breaking changes being pushed as default for some inexplicable reason.
Re: My take on the current React and Server Components controversy
#9As soon as React started suggesting using a framework for their framework, the writing was on the wall. Nested frameworks are like the private equity and financial sector, smoke and mirrors abstraction that delight some, offend others, and make a small group richer and richer. The churn of “progress” is exhausting man
Re: My take on the current React and Server Components controversy
#10As soon as React started suggesting using a framework for their framework, the writing was on the wall. Nested frameworks are like the private equity and financial sector, smoke and mirrors abstraction that delight some, offend others, and make a small group richer and richer. The churn of “progress” is exhausting man
Its frameworks all the way down