![]() ![]() At the same time, this allowed the application’s data to be stored remotely, freeing the user from a single PC. Essentially, perform the heavy lifting on a server somewhere, and deliver a lightweight interface to the user via HTML and javascript. The web introduced a hybrid model where some of the processing still happened locally, but most of the processing happened remotely on a server. All processing was done locally, and all data generated by the applications was also stored locally. In the golden days of Windows, we didn’t even try - you would go to the store and buy one or more physical installation disks, then install and run the software on your PC. We moved from a world of text based terminals to GUIs and real-time rendered 3D video, and with those things dramatically more data to ship around. Since you couldn’t really do much with the machine, these types of thin clients could pretty much do anything you could do locally, albeit with added latency.īut as technology progressed, the incredible experiences a computer could create locally greatly outpaced our ability to deliver these experiences remotely. A few decades ago, when computers were much scarcer, this used to be the default way of interacting with a computer via Teletype or the like. ![]() The dream of the thin client - one that could be good enough not just for basic computing tasks, but even highly demanding tasks such as gaming - has long eluded us. Today we’re proud to announce that we’re adding support for the Raspberry Pi. Last autumn we released Parsec, a standalone cloud gaming system that can be used to play games remotely, either on your own PC or in the cloud via AWS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |