Комментарии:
my sincere condolences for the small editing mistake lol
ОтветитьIf the devs would actually care about the performance they wouldn't use react in the first place
ОтветитьHi I am using next js 13 app deployed on amplify aws but it gives me html chunks code after some time please tell me any solution.
Ответитьcan u make a project using T3 stack plz , it been a while that u have uploaded a detailed project video .
ОтветитьNextJS is becoming trash since the app router trust me, i faced a loooot of bugs and weird issues that are nowhere to be found in the nextjs/react community
Ответитьthat Nokia is 2000 mister
ОтветитьGonna switch to php at this point
ОтветитьBoth client and server components are important as they both have a role to play.
ОтветитьThese whole web framework companies and communities need to chill. A $50 android device can handle downloading code just fine. I bought one just to see what the low-end models were experiencing. Everyone is trying to get .001 second increases and speaking to others as if they need to rethink how they do things. The experience for users is not a problem. People need to put time into thinking why they have 0 users using their apps before they keep switching their toolkit.
ОтветитьWasn't how it was before it moved to client data handling? Now, we going back to server and then we move back to client once again... @marufbepary100 seem to have right idea or are we talking about an even better way?!
ОтветитьUmmm, one word. Astro
ОтветитьU guys should just say use php instead. Wth! 10yrs time you will change scope again... really crazy
ОтветитьWhy don't you guys just learn htmx and stop with this nonsense? It's honestly getting ridiculous the amount of mental gymnastics you guys have to do to defend react at this point.
ОтветитьTell the article writer to use PHP or something else.
Ответить🎉 I like client components
ОтветитьReactJs was really not designed for this whole SSR... I am moving to SvelteKit
ОтветитьI tend to say make every page a server component and then you can use client components inside of that page. That way you can do all the fetching directly from the server and then pass it down to the client components without creating APIs. If you can use server component then you should but client components are still needed.
ОтветитьNow there is more confusion😢
ОтветитьHey Josh, awesome video as always, about the topic, as I am also working mainly with NextJS (still preferring the versions prior 13) I have started doing few hobby projects on the latest version, and what I am experiencing is hard times. In my honest opinion Vercel's team have to think about making something in-between(client and server), like state management can't be avoided everywhere and so I guess version 13 contributed not that much as caused frustration and negative impact, however think that within short period of time we will have best of both worlds of React and PHP. Anyways, keep up the good work!
ОтветитьYeah this article is crazy (and I imagine just clickbait to get a reaction out of people).
React was literally invented to create dynamic, responsive, interactive user interfaces - which you can only do on the client. That's like trying to build a mobile app but not wanting to put any of the code on the users phone.
Next.js does a good job allowing us to do SSR / incremental regen, fetching data on page requests etc but if you actually want your web app/site to do anything dynamic you will always need client side code (stateful logic etc). I'd argue if you're not doing anything dynamic then you don't need to be using React in the first place (except for a nicer dev experience maybe).
I understand the benefit of only shipping the necessary clientside code vs shipping all application code by using server only components, but this article seems to suggest no clientside code which I really don't understand 🤷♂
If we ditch client components entirely, we might as well switch to php. At least caching will be manageable.
Ответитьbro please attach the article link.
Ответитьthis take of the balance between server and client architecture is 100% correct. we simply cant default to client only or server only. this isnt 2014 anymore. code splitting is easier than ever, and we should use it to our advantage. P.S.: using TRPC + react query on the server AND on the client has been the easiest way to build performant web apps that ive seen to date. and it even covers use cases for scalability that allow you to migrate your TRPC routes to a separate BE over time and use TRPC as a proxy....so this whole no-client-side argument is honestly just total react hating garbage.
ОтветитьWhy is everyone so against code running on the client? Client devices are so capable in 2023
Ответитьso this article said we must go back to php ? good
ОтветитьHej Josh 👋 I am just dreaming here but that would be awesome a recorded hour talk (podcast?) with the author of the reddit post, where both of you would confront your ideas and discuss that topic and claims <3. Danke schön for the video!
ОтветитьEveryone is talking about the "render on server === faster app" advantage but noone is talking about the cost of processing all that rendering.
With "normal" React app, the clients actually do all the processing, so we don't need to care too much about scalability/performance optimization on the server side.
But with server side rendering... let's just say that you should prepare for a (much) bigger Vercel/AWS bill at the end of the month in comparison to client side React app, not to mention the cost of hiring a Primagen to help you optimize all your infra
.
Moreover, we've been using Client Side React for years and now someone is still bringing up the "what if client uses an old device?" argument, I mean really? Just use Astro or PHP + HTMX bro
Idk man, using nextjs for a website that is mostly server rendered and has bunch of interactivity sprinkled in sounds ridiculous to me since there are much better alternatives for that. But that's what nextjs developers are pushing for. I just want my highly interactive web app to be able to show itself quickly on the browser and also have good SEO. That's all I want from nextjs.
ОтветитьServer sided components are incredibly overrated
Ответитьplanning to move back to good old PHP. damn..they don't give me sh*t.
Ответитьmy grandpa said..php lives.
ОтветитьShould we just use Astro?
ОтветитьLike it or not, he is right, i love the new nextjs 13 app directory
ОтветитьNextjs gives us best of both worlds, Server + client ✓✓✓
ОтветитьNo no bro, I don't agree that. That is a feature not an issue. I have been depending on that for lots of my projects, I might need to change whole stuff if Nextjs does something (which removes that caching behaviour).
If you need any of your pages not to be cached please use <a> tag instead of <Link>...✓✓
Bro kindly make a video on how to handle delay in loading ui whenever the page reloades in next 13 it was so horrible the entire layout of the website is shifting on page reload
ОтветитьThere is a reason it’s called React .
Ответитьjosh finally swallowing the CSR pill? didn't think i'd live to see the day.
ОтветитьI don't get it. Isn't the best of all worlds that we get fine-grained control to use server and client as it best fits the use case?
Also, re client components vs server: sure, the client has to download a bunch of javascript files but the entire process isn't just downloading but processing and rendering data. Let's say you have charts you need to display based on data; isn't it very inefficient to have the server process and render for every client those graphs when it can just ship the raw data and "instructions to make the graph" (javascript files) to the client so that computing power gets off-loaded to the client's device and the server only has to worry about sending the plain data?
Yeah I'm going back to intercoolerjs I mean htmx and php you all have fun...
ОтветитьWhen i stop and think about it, i can't even remember if i've ever written a component without `useState` or `useEffect` or `useMemo` or 'onClick` ... i really don't understand the point of RSCs.
ОтветитьPurely client side is not fun, Purely server side is also not fun, A good mixture of both and knowing when to use which is where it gets very good
ОтветитьWorst clickbait video.lame man
Ответитьbig Josh W, no more words are needed
ОтветитьDeno
ОтветитьSorry but that argument makes zero sense. Server side components are pretty useful for fetching and static sections of the page (header, footer or even certain static sections of a page). Otherwise, client side components are all the way. If someone wants to ditch client side and use server-side excessively, he should ditch nextjs entirely and use Astro, node+express or even php.
ОтветитьMaybe when server actions become stable, a lot may change.but even server actions has a client hook 😂😂
ОтветитьHey Josh, You are building your SaaS in app dir with all use client thing 😂 or going back to OG pages?
Ответить