Lin Clark on WebAssembly

There are several computer science students (including myself) who before entering the major had already some hands on experience with programming. I would dare to say that most of them started programming web pages. We all understand the basics, first put some HTML to define the structure of the page, then add CSS to style the page, some Javascript to add dynamic content and finally use your preferred programming language for the backend. In my case, the programming language which I used was PHP. 

Nowadays, web applications turned out to be the next big thing. Many years ago, people used to download and install a software using a wizard or running some script to store the program in their computer, but now, this has changed. Now, the programs are not stored in the clients' storage, they are stored somewhere else (mainly in the cloud or a web hosting). So that raises the question: How users can access these applications? By an amazing software called the web browser. 

I am still very curious about all the implications of adapting to the client-server architecture, especially in the web. There are a wide of concepts and technologies involved in the process (and they continue to develop new ones). The HTTP protocol defines the set of rules for how web browsers need to address to the servers running the applications. 

Looking forward to new technologies like functions, containers and K8s clusters. They are the main reasons why innovative companies move to a new architecture system design called microservices. In order to become a master, of course first you need to have strong knowledge of the basics of how web browsers work, HTTP protocol and Web Assembly. I don't know, maybe in the future we will not require to have videogame consoles to play but rather just a computer with internet access.

Comentarios

Entradas más populares de este blog

Internals of GCC

The future of programming languages

Welcome