Breaking up with JavaScript front ends

Re:Breaking up with JavaScript front ends by arcturus17 on Saturday December 10, 2022 @07:12PM (#33938490)

I don't understand the "right amount of control" bit, there are plenty of options to control what data moves to and fro in NextJS, but the CEO of Vercel has replied to you in a sibling comment; he's going to be able to address your technical concerns better than me.

I'll just add that I'm not familiar with either of those sites, because I'm sitting in Spain and neither operate here, but on first inspection the UX has felt brilliant to me - particularly Walmart's. Everything loads very fast, the search is great, etc. I cannot say if their code or eng practices are a tire fire but the product looks good to me.

[ Parent | on HN ]

Re:Breaking up with JavaScript front ends by CharlieDigital on Sunday December 11, 2022 @11:45AM (#33944749)

> I don't understand the "right amount of control" bit

Try Astro.js and you'll understand. If the data has been used to SSR and has no function on the client side, don't send it to the client.

If two multi-billion dollar, multi-national corporations with multi-million dollar project teams can't get it right in a space where every ms counts, then the average team has no hope.

[ Parent | on HN ]

Re:Breaking up with JavaScript front ends by medbrane on Sunday December 11, 2022 @03:02PM (#33946891)

What you ask for is now possible using Next.js and the new React Server Side components. Check the link in the sibling comment tree.

[ Parent | on HN ]

Re:Breaking up with JavaScript front ends by Rauchg on Sunday December 11, 2022 @03:48PM (#33947329)

That's definitely what RSC accomplishes, which I mentioned in my comment.

[ Parent | on HN ]