Qwik the Faster Front-end Framework
Qwik is a new kind of web framework that can deliver instant loading web applications at any size or complexity. Your sites and apps can boot with about 1kb of JS (regardless of application complexity), and achieve consistent performance at scale. — qwik.builder.io
I know it’s probably been 0 days since another javascript framework have been released, but before you change your mind and stop reading this is not just an average framework, it’s bring an entirely rendering paradigm to the table called resumability.
Resumability
The best way to explain resumability is to understand how the current generation of frameworks are replayable (hydration).
These frameworks have to add interactivity to server-rendered HTML.
Qwik is different because it does not require hydration to resume an application on the client. Not requiring hydration is what makes the Qwik applications startup instantaneous.
Resumability is about pausing execution in the server and resuming execution in the client without having to replay and download all of the application logic.
Zero hydration
This means in theory you should be able to a perfect lighthouse performance score no matter how big and complex your javascript code base is.
How is this possible?
The quick innovation here is that a Qwik app can be fully serialized as HTML in other words at any moment you can hit an action and capture all the data and closures in the application and represent all as an HTML string.
That’s huge for server-side rendering because by the time that HTML gets to the browser it can just pick up where the server left off without need to execute any javascript at all and that’s why they coined the term resumability.
Auto Lazy Loading
Lazy-loading is asynchronous. Qwik is an asynchronous framework. Qwik understands that at any time, it may not have a reference to a callback, and therefore, it may need to lazy-load it. (In contrast, most existing frameworks assume that all of the code is available synchronously, making lazy-loading non-trivial.)
Let’s look some code:
Notice the presence of $ in the code. $ is a marker that tells the Optimizer that the function following it should be lazy-loaded.
This means that javascript will not loaded until we click the button it contains the code that we want to execute, and also has access to the lexical environment to update state that might be shared by other components which itself comes from another lazy-loading chunk.
The take away here is that you don’t need to load any javascript until the user interact with the UI.
Qwik can scale infinitely to as much JavaScript as your heart desires.
