Miško Hevery explains blazing fast Qwik JS


Miško Hevery is the CTO of Builder, the online visual site designer. He is also the creator of Qwik, a next-generation JavaScript framework. Before his Builder and Qwik days, Hevery created Angular, one of the flagship JavaScript frameworks, and Karma, the popular JavaScript test runner.

Clearly Hevery has a long history of involvement in the JavaScript world. I had a chance to talk with him about Qwik, Builder, reactivity challenges, speeding up web apps, helping content creators and engineers coexist, and more.

Matthew Tyson: I’m excited to talk to you. I discovered Qwik, and that led me to Builder and your bio. You have a really interesting history, including the creation of both Karma and Angular, so I’m eager to hear what you think about some of the latest JavaScript trends.

Let’s start with reactivity. Reactivity is one of the most significant developments in front-end code, but it is not a perfect world.

Miško Hevery: It is complicated. Reactivity has many great properties, but also many problems. The basic issue with reactivity is that it requires a lot of compute resources to set up and then to tear down. This negatively affects the performance and memory utilization. The implication of all of this is that a framework must download all of the application before reactivity works.

Qwik needs to be reactive, because we want to be lazy, but at the same time we need an approach to reactivity which allows the framework to reason about the application without loading it. Qwik does this by storing reactive subscription information in the DOM.

Copyright © 2021 IDG Communications, Inc.





Source link

Leave a Comment

Your email address will not be published. Required fields are marked *