Always amazes me how the industry goes back and forth between thick and thin clients. In the 90s it was all thick. With HTML it went thin. With Applets it went thick. With better browsers it went thin. With single page interfaces (SPIs) it went thick. Can we get off this teeter-totter?
Thanks for the video. Doesn’t it all depend on how the computer is used? In other words, if I’m using MS Word to create a document, it’s a thick client. But, if I’m using a web browser to surf the web I’m in thin client mode.
Not exactly. You can download apps onto Chromebooks, so data can be stored onto the device. They can be used AS thin clients, but there are security threats that you don't have with true thin clients. Read more here: searchvirtualdesktop.techtarget.com/news/450423125/Android-apps-on-Chromebooks-hurt-appeal-as-thin-clients?Sthinclients&?Offer=OTHR-youtube_OTHR-video_OTHR-thinclients_2020September29_thinclients
=( the points you make here are misleading and can be quickly exposed as false, e.g. the statement that thinclients are more secure against attacks than fatclients is false because either way the hardware has to be implemented and purchased against manipulation and the software is available on both systems and offers the same protection. a real advantage for example, would've been the mention that with thinclients only the executing VM/Server needs protection, while with fatclients this must be present on every device. The danger remains nevertheless the same... depending on how the guidelines for the user are set and what they're allowed to do and what they're not. Less power - did you calculate the power consumption of your server / s because you need redundancy unless you want your lemmonade stand to have a full fallout, the required UPS as well as Server cooling: recirculation air conditioners and room air conditioners into your equasion? Sorry Also ultrathinclients do have storage, please dont be a baffoon just grab one and open them up and have look inside im sure you'll find some sort of local storage since it is needed otherwise the system would not function for example L1 L2 L3 cache is considered local storage, you could rather say that the difference is that there is no local storage that can be used by the user, that would make more sense.(aka no local GUI Operating System but some sort of shell that makes the execution of PCoIP, HDX, or RemoteXX possible while everything else is happening on VDI DaaS)
this made a lot more sense than the comptia a+ book i am reading. thank you
Glad it was helpful!
the music is so loud its distracting
Always amazes me how the industry goes back and forth between thick and thin clients. In the 90s it was all thick. With HTML it went thin. With Applets it went thick. With better browsers it went thin. With single page interfaces (SPIs) it went thick. Can we get off this teeter-totter?
Brilliant choice of music! 🎉
Thick client is a workstation. Thin client is a Server.
Thankyou so much...😊😊😊😊😊😊
Most welcome 😊
Nice explaination, but the music is waaay too loud.
Thank you for the valuable info!!
You're welcome!
Thanks for the video. Doesn’t it all depend on how the computer is used? In other words, if I’m using MS Word to create a document, it’s a thick client. But, if I’m using a web browser to surf the web I’m in thin client mode.
Digestible, that was delicious 😋 thank you
Glad you liked it!!
Good explanation!
Glad you think so!
Good video.
Thanks!
So chrome book is a thin client
Not exactly. You can download apps onto Chromebooks, so data can be stored onto the device. They can be used AS thin clients, but there are security threats that you don't have with true thin clients. Read more here: searchvirtualdesktop.techtarget.com/news/450423125/Android-apps-on-Chromebooks-hurt-appeal-as-thin-clients?Sthinclients&?Offer=OTHR-youtube_OTHR-video_OTHR-thinclients_2020September29_thinclients
Thanks!
Welcome!
Can a thin client be used as a raspberry pi?
Yes, a Raspberry Pi can be used as a thin client!
I could not end the video. The music is unbearable!!
We feel you -- we hope we're doing much better with our recent videos!
=( the points you make here are misleading and can be quickly exposed as false, e.g. the statement that thinclients are more secure against attacks than fatclients is false because either way the hardware has to be implemented and purchased against manipulation and the software is available on both systems and offers the same protection.
a real advantage for example, would've been the mention that with thinclients only the executing VM/Server needs protection, while with fatclients this must be present on every device.
The danger remains nevertheless the same... depending on how the guidelines for the user are set and what they're allowed to do and what they're not.
Less power - did you calculate the power consumption of your server / s because you need redundancy unless you want your lemmonade stand to have a full fallout, the required UPS as well as Server cooling: recirculation air conditioners and room air conditioners into your equasion? Sorry
Also ultrathinclients do have storage, please dont be a baffoon just grab one and open them up and have look inside im sure you'll find some sort of local storage since it is needed otherwise the system would not function for example L1 L2 L3 cache is considered local storage, you could rather say that the difference is that there is no local storage that can be used by the user, that would make more sense.(aka no local GUI Operating System but some sort of shell that makes the execution of PCoIP, HDX, or RemoteXX possible while everything else is happening on VDI DaaS)
:O thank you computer lady, i have athick client computer
You're welcome, and thanks for sharing!
That's thick!
I understude....😊
Tnx but music is annoying
Sorry to hear! Thank you for the feedback -- we will take this into consideration for future videos.
Pls keep the music down
Thanks for the feedback! We've come a long way in the years since 😊