Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My take on the current React and Server Components controversy

phryneas.de

Post reply on HN
Print view View original

71–78 of 78 posts

Re: My take on the current React and Server Components controversy

#71

Post by quickthrower2 »

z3t4 wrote: post #45
bob1029 wrote: post #23

How many of us are working on web applications that legitimately cannot be served as basic, server-side web forms with JS only as necessary for dynamic client-side UI (e.g. disabling buttons upon form submit)? How are things like SPA improving the end user's experience and/or adding value to the product? If you are struggling and want a no-bullshit stack, why not PHP or string interpolation in your favorite language?…

You don't even have to write document.getElementById as all html ID`s are global variables.

Wot! That is insane. But what if the id you want is a value in a string?

Re: My take on the current React and Server Components controversy

#72

Post by hardex »

bob1029 wrote: post #23

How many of us are working on web applications that legitimately cannot be served as basic, server-side web forms with JS only as necessary for dynamic client-side UI (e.g. disabling buttons upon form submit)? How are things like SPA improving the end user's experience and/or adding value to the product? If you are struggling and want a no-bullshit stack, why not PHP or string interpolation in your favorite language?…

> If you are struggling and want a no-bullshit stack, why not PHP or string interpolation in your favorite language?

Found the guy responsible for the shitty local government websites leaking data left and right.

Re: My take on the current React and Server Components controversy

#73

Post by madeofpalk »

quickthrower2 wrote: post #71
z3t4 wrote: post #45

Earlier quoted context omitted.

You don't even have to write document.getElementById as all html ID`s are global variables.

Wot! That is insane. But what if the id you want is a value in a string?

window[myElementsId]

Re: My take on the current React and Server Components controversy

#75

Post by shipscode »

datavirtue wrote: post #50
shipscode wrote: post #32

Earlier quoted context omitted.

I'm in the same boat. Redux + Pre-Hook React was very legible & straightforward... Post hooks React is strong on theory but weak on substance, and I've gone to just jQuery and Python for my latest project. I did migrate my last project the barebones JS MVP -> React and regretted it immensely. It took about a month and didn't provide enough value to make it worth it.

I tried to learn React during the transition. Thankfully I had the authority to nope-out after trying to build a few apps with it and running into nothing but tons of arguing online when trying to search for help on what I thought would be an easy five minute task: to find out the best way to track state in my app.

Yeeeep. The arguing by clout chasers was the worst part.

Re: My take on the current React and Server Components controversy

#76

Post by orneryostrich »

bob1029 wrote: post #23

How many of us are working on web applications that legitimately cannot be served as basic, server-side web forms with JS only as necessary for dynamic client-side UI (e.g. disabling buttons upon form submit)? How are things like SPA improving the end user's experience and/or adding value to the product? If you are struggling and want a no-bullshit stack, why not PHP or string interpolation in your favorite language?…

This is fine advice for a personal project, but I don’t recommend proliferating a new custom framework if you expect other people to join and ramp up on your codebase. It’s nice to be able to join a shop that’s using something you’re already familiar with.

Re: My take on the current React and Server Components controversy

#77

Post by orneryostrich »

bob1029 wrote: post #28
AgentME wrote: post #26

Earlier quoted context omitted.

I'm not sure you understand what React Server Components are if you think server-side web forms with only the necessary client-side JS is in opposition of it instead of being exactly what it's about.

> I'm not sure you understand what React Server Components are Not in depth, but that's kind of my point. I don't really need to anymore.

You never “need to” learn much of anything, but I think it would give you a different perspective. You don’t know what you don’t know.

Re: My take on the current React and Server Components controversy

#78

Post by synergy20 »

bob1029 wrote: post #23

How many of us are working on web applications that legitimately cannot be served as basic, server-side web forms with JS only as necessary for dynamic client-side UI (e.g. disabling buttons upon form submit)? How are things like SPA improving the end user's experience and/or adding value to the product? If you are struggling and want a no-bullshit stack, why not PHP or string interpolation in your favorite language?…

There are many use cases where server components making no sense:

    1. RESTful or API sites that just need a SPA to render
    2. embedded boards that can never run node.js etc, there are millions or billions of them.
    3. Eletron.js or React Native related applications, why do I need a next.js alike component involved at all?
Mixing SPA with SSR into React makes thing unnecessarily complicated, can SSR be an opt-in component just like what it used to be, so us SPA users do not need know your yet another revolutionary goodies that everybody must love it or he/she has no clue what's the best right now?

I switched from Vue to React, now it seems I must switch back as Vue still separates SSR from CSR, god knows how long will that stay.

Post reply on HN