Hello readers, welcome to my new article on web worker communications. I hope you enjoyed my previous article on multi threading on the web. In this article, we will discuss how to scale web workers and handle worker responses more efficiently.
Hello awesome readers, hope you are having a great time. Today we will discuss a performance issue on the web and how to solve it using workers and multi-threading. Before we start, let's understand what is a thread and how it works?
Rendering is the process of constructing the DOM tree, creating the frames, and showing it on the screen. Generally, it consists of multiple steps known as the Critical Rendering Path(CRP).
It is said that a fresh mind is easier to train than the one already trained in something !!
Switching to a new frameworks is not easy. I think that is true for experienced developers specifically. Since we have already developed a mental model and understanding of the earlier framework. The same thing happened to me when I decided to explore React JS a few months back. Being an Angular developer initially, I found it a little difficult to wrap my head around the new concepts. Back then I used to think in Angular and convert it to React. It's like learning a new language, where we try to think in our native language and then translate it. Eventually, we get the hang of the new language and no longer require translation.