The Browser based Client OS
5th Oct 2016
The Browser based Client OS
Present and Future
The idea of using a browser to replace the traditional operating system is central to the future of cloud computing and is one (idea) that many on the forefront (of cloud computing) hold very dear. In order for cloud computing to be deemed truly successful it needs to be able to wane users from reliance on personal hardware, software and storage. In fact, browsers are fast becoming a topic of interest that is almost parallel with that of operating systems (just perform a simple Google search to confirm); in many circles, they have surpassed the OS as a central focus. This doesn't mean to imply that operating systems are going the way of the dinosaur, far from it; they're simply being migrated away form users and into remote hardware stacks. In other words, the browser is moving closer to the consumer and the OS is moving farther away.
What purpose does a cloud computing OS actually serve? They function in ways that are typical or familiar, but a cloud operating system is much more a series of logical processes that hold together and 'direct traffic' for the various software, hardware and virtualized hardware/software processes that compromise a user system. A cloud OS essentially a hardware site interface construct that responds to the commands given by a browser or client OS.
Referring to a browser as an OS is actually a bit of a misnomer, because the actual operating system is not reflected in the construct or design of the browser itself; it simply provides a gateway that allows users to connect to the on-site OS which actually does the work. The actual cloud OS, which is responsible for the advanced functions of a virtual computer, will likely be inaccessible for most individuals on the user-end. Modifications of any OS will likely be left in the hands of the cloud manager, which may even be a third party participant if a cloud provider has outsourced this position. It is still unclear how 'modifiable' cloud components will be in terms of individual component customization.
Many of the mobile browser models (that are currently in use in cell phones and tablets, for example) are providing the inspiration that is leading to the development of better and more complex browser client operating systems. Experts in the field of cloud development can essentially use the lessons learned from the overall effectiveness of different mobile device browsers as a form of research and development.
There is one area of concern (over the browser OS) among potential cloud users and initiates however; and that's a worry over a lack of central features. Many individuals seem to feel that a lack of personal hardware / software resources is going to translate directly into poor performance and/or memory loss. Developers have devoted a lot of time and money toward creating solutions for a whole host of contingent issues related to performance and reliability. These solutions include ideas such as the implementation of minimal storage units that are designed to provide buffers between the client browser and the host resources in the event of disconnect from the net. When the client reconnects, information is transferred and synching is performed automatically. In terms of performance, the average connection speed has been steadily increasing year after year since the internet was established. It is estimated that by the time cloud computing takes over, many individuals throughout the world will be utilizing fiber-optic based connections which will provide speeds at or above T1.
The actual role of the browser OS will obviously be much more intensive than the kinds of operations that we currently associate with the term 'browser'. The actual cost of connectivity is lowering day by day and the idea of having a remotely located system is beginning to look more and more attractive as well; this essentially translates into the browser OS 'picking up the slack' that used to be handled by traditional operating systems.
Individuals in today's world possess computers that are extremely powerful in scale, yet they rarely (if ever) actually use even half of these resources. After starting up, most people go straight to their internet browser of choice; all of the hardware resources from these millions of individuals are basically going to waste. The point is that the client-server model has essentially morphed into a form of cloud computing (anyway). The average person uses the internet for virtually everything, and all of the information, resources and processes are usually remotely located and accessed via the net. The only difference between this and cloud computing is that hardware resources are not wasted.
Currently on the net there is a big push from individuals and groups to participate in the open-source development of a more comprehensive browser OS for cloud computing. It is a tactic that has been successfully applied by other organizations; most notably the Magento platform, who are one of the leading developers / purveyors of eCommerce software and design. The idea is to cut costs while at the same time opening up access to a much larger pool of ideas from individuals that would otherwise (through traditional development means) never be able to provide input.
The development and implementation of a truly great browser OS will mark the beginnings of a brighter future for cloud computing in general. It may very well be that browser-client operating systems (through cloud computing) will only appeal to a select group of individuals at first. But over time, (as with other organizations that were initially apprehensive about cloud computing) their abilities and beneficial traits will be broadcast throughout the world, leading to more widespread use.