I don’t disagree with your explanation of a thin client. I do however think you are missing the point about how a Chromebook works. Not that different of a concept really. With a Chromebook how does an average user edit a paper, a presentation, a spreadsheet? It’s all using google cloud services. Connecting to their servers to edit files an save them. Running a slim version of Linux they made essentially to get you on the web to use their services. Not too dissimilar to an arm version of windows to connect you to MS cloud services.
Like I said, not for me but then again I switched from Windows to Linux due to the recall “feature” and have run various Linux servers for decades now. XBMS with Samba server was the coolest thing ever at the time.
Its not for me but how is this much different than using a chromebook? I wouldn’t say Gross, just not for me just like the chromebook.
It is a different concept.
With a Chromebook, the user interacts with a local session.
With a thin client, the user interacts with a session running on a server, the thin client just connects to the session like an RDP connection.
I don’t disagree with your explanation of a thin client. I do however think you are missing the point about how a Chromebook works. Not that different of a concept really. With a Chromebook how does an average user edit a paper, a presentation, a spreadsheet? It’s all using google cloud services. Connecting to their servers to edit files an save them. Running a slim version of Linux they made essentially to get you on the web to use their services. Not too dissimilar to an arm version of windows to connect you to MS cloud services.
Like I said, not for me but then again I switched from Windows to Linux due to the recall “feature” and have run various Linux servers for decades now. XBMS with Samba server was the coolest thing ever at the time.
That is fair, I didn’t consider that type remote connection to be a thin client, but you are right.