I don't know how many resources I've read/watched that explained the difference but didn't show it. I just couldnt grasp it until now. This helped so much, thank you!
So if I get it correctly if the website is hosted up on an extremley fast server you get this instant page loads right? And then the dynamic content that NEEDS to be rendered on client side is being loaded there but you already see the rest of the page, this is freaking cool.
Haha thanks I picked up on the accent - all my favourite movies are Kiwi (whale rider, hunt for the wilder people) and I've watched so much 'How To Dad' on UA-cam and I love artists like Princess Chelsea - i realised quite far into the video that you weren't just Australian. Please humour me, I'm British!!!
So the initial HTML is SSR because it comes direktly from the server, the and part with the fruit is CSR, even tho the information comes from the server, but in the end is rendered by the client.
Is there an app in Chrome that identifies on the front end browser which elements are not SSR? And in addition which data on the front is not being parsed by SSR? So for example I have seen product URLs not SSR, no html a href tags which is problematic for SEO? Something to see quickly rather than investigating and inspecting elements?
I get where you're coming from, but the premise of "2 processes rather than 1" isn't 100% accurate. Something has to process the data to make the HTML representation, so if that is completed server side that means 1 longer process rather than 2 short ones (you're not magically removing the need for that process, just shifting which side is responsible). As such if you heavily rely on data formatting you need to scale your server resources to cater for this - so I just don't get how it's such a big saving on time?
Cheers for watching 💛 Get hired faster with a better resume @ www.hyr.sh
I don't know how many resources I've read/watched that explained the difference but didn't show it. I just couldnt grasp it until now. This helped so much, thank you!
Glad it helped :)
Love this explanation, straight forward with example! Thanks a lot for this
Finally someone who can actually explain it.
Cheers broski :)
This video is worth more than a ton of blogs
Simple to understand and beautifully explained, thank you so much!
Great and simple explanation! Thanks!
To the point, best explanation so far
Couldn't make it clearer. thank you !
glad you found it helpful :)
What a bos!! u literally showed us the difference, by not just explaning it niec!
So if I get it correctly if the website is hosted up on an extremley fast server you get this instant page loads right? And then the dynamic content that NEEDS to be rendered on client side is being loaded there but you already see the rest of the page, this is freaking cool.
it's freaking cool indeed!
Great insight, nice to know that a combined approach can open more options for an app. TY
glad you enjoyed :) thanks for the support too
Man thank you so much, simple and informative, wish you all the best.
I can say that this is the explanation i wanted to hear 😅
Clean and on point explanation! Thank you.
Glad you enjoyed it :)
Thank you! Such a simple explanation! :)
Oh! Such quality content! Love this!
Thanks for the comment!
great explanation! thx buddy
Great content! Straight to the point and just enough detailed. Btw whats that theme?
Glad you enjoyed :) and it's 'Tomorrow night blue'
Very clear explanation, thanks so much.
Happy it helped my friend :)
Great video explaining the advantages/disadvantages of each!
Excellent way to explain this. Thank you
Happy to be of service:)
Great video with example.
man, you did it clear as possible!!!!
Glad you found it helpful :)
Oh my gosh amazing video informative and helpful. Are you in New Zealand?
Glad you found it helpful! And yes I am in New Zealand - good guess haha
Haha thanks I picked up on the accent - all my favourite movies are Kiwi (whale rider, hunt for the wilder people) and I've watched so much 'How To Dad' on UA-cam and I love artists like Princess Chelsea - i realised quite far into the video that you weren't just Australian. Please humour me, I'm British!!!
nicely explained, thanks! :D
Awesome Video, this is the best video on these
Thanks
So the initial HTML is SSR because it comes direktly from the server, the and part with the fruit is CSR, even tho the information comes from the server, but in the end is rendered by the client.
And it's best easiest explanation
Cheers broski :)
Jazakallah🥰
Doesn't SSR take more resources on your server since it's gonna be the one generating the page?
Not always - a lot of services build the static server pages once and cache them and it's very efficient
yesus that's very blue
Is there an app in Chrome that identifies on the front end browser which elements are not SSR? And in addition which data on the front is not being parsed by SSR? So for example I have seen product URLs not SSR, no html a href tags which is problematic for SEO? Something to see quickly rather than investigating and inspecting elements?
Hello the video is very helpful for me . can you share this codes?
Thank you
like ++. super tnx , fast and to the point
thank you!
What happens if you have css?
thanks for sharing !
Hey...
Can you make video for ssr in react v18 from scratch?
I sure can 😊
You're awesome
Thanks
great video!
Cheers broski!
Good video
Tyvm my friend :)
Nice explanation - your CSS is taking ages to load though ;-)
Haha man's got an eye for detail
I get where you're coming from, but the premise of "2 processes rather than 1" isn't 100% accurate. Something has to process the data to make the HTML representation, so if that is completed server side that means 1 longer process rather than 2 short ones (you're not magically removing the need for that process, just shifting which side is responsible). As such if you heavily rely on data formatting you need to scale your server resources to cater for this - so I just don't get how it's such a big saving on time?
Cache
❤❤
Very nice man! fr
0:25 honk
4692 Stokes Tunnel
West Views
Abcd