Thin clients are fine, naive one will have no sound and no way to use USB drives (which might be a sought after feature!) and no 3D or OpenGL either but what works? everything else.
You can browse, use word processors, youtube in the small video size works, use terminals, run image editors.
You can mix them with thick clients, if the latter have /home mounted on NFS or are Windows machines with user accounts in Active Directory. The admin can be an asshole that locks everything out either way, or give you a normal desktop and a decent amount of software to work with.
So people can do 3D or multimedia on the same user sessions run from thick client..
Now if you mix local and remote on the same seat that's more complicated. I think the appeal would be to not bog down the application server with web browsers (running 20-30 or more browsers in the year 2018 must be something).
Also, "VDI" infrastructure sounds exactly like the kind of things made to benefit vendors and complicate things : if you're going to run one Windows 7 VM or one Windows 10 VM per user I don't see where you're saving resources much (but providing a new image may happen very quickly in the engine room, versus slowly transferring gigabytes to the user's seat)
It's more fun with linux, you can do like it's the nineties when organizations did it with big Unix machines , run 20 users on a single OS and there are no licensing costs (for the OS itself).
You can browse, use word processors, youtube in the small video size works, use terminals, run image editors.
You can mix them with thick clients, if the latter have /home mounted on NFS or are Windows machines with user accounts in Active Directory. The admin can be an asshole that locks everything out either way, or give you a normal desktop and a decent amount of software to work with.
So people can do 3D or multimedia on the same user sessions run from thick client..
Now if you mix local and remote on the same seat that's more complicated. I think the appeal would be to not bog down the application server with web browsers (running 20-30 or more browsers in the year 2018 must be something).
Also, "VDI" infrastructure sounds exactly like the kind of things made to benefit vendors and complicate things : if you're going to run one Windows 7 VM or one Windows 10 VM per user I don't see where you're saving resources much (but providing a new image may happen very quickly in the engine room, versus slowly transferring gigabytes to the user's seat)
It's more fun with linux, you can do like it's the nineties when organizations did it with big Unix machines , run 20 users on a single OS and there are no licensing costs (for the OS itself).
Comment