Qwik: A no hydration instant on personalized web applications by Misko Hevery

Qwik is a new bread of frameworks with a goal of instant-on interactivity for your site even on low-power slow-network devices. Qwik is a resumable framework that starts its execution on the server and seamlessly transitions to executing on the client in a very lazy and incremental way. The seamless transition from server to the client provides an instant on-user experience which leads to lower bounce rates, more conversions, and higher sales.
With Partytown for third-party scripts, and Qwik for your first-party applications your browser main thread has never been so bored. Qwik and Partytown are new bread of open-source web technologies that are designed with startup performance first as the main objective and all other design decisions follow from that goal. When Qwik and Partytown are combined with an edge-delivery network it is possible to get your application fully interactive into users' hands in as little as 50 ms setting a new standard of startup performance.
MISKO HEVERY
As CTO, Miško oversees the technology division that powers the Builder.io applications and software. Before joining Builder.io, he created Open Source platforms for Google, including Angular, AngularJS and was co-creator of Karma. While at Google, he brought a testing culture there with his blog. Before focusing on making the web better, he believes testing is the key to success.
Miško started his career designing digital circuits and moved to databases, full-stack development and finally, front-end frameworks, giving him a unique perspective. He understands all of the layers from the web down to a transistor. In addition to Google, he worked for tech powerhouses Adobe Systems and Sun Microsystems.
He holds an MS/BS from Rochester Institute of Technology and an MBA from Santa Clara University.
------------------------------------------------------------
INTRO
visuals & editing by @Mercator
music : Avocado by Ephixa

[@fifty6737]

hands down the best web framework, fast, elegant, simple to work with

[@mustafe1391]

history is being made in front us.

[@RaphaelRafatpanah]

Oh wow, it’s great to see Qwik address major problems within the e-commerce industry (and web dev in general). Also, I was wondering what the offline story was and I was quite pleasantly surprised. Absolutely amazing!

[@efrenUtube]

Absolutely amazing!, great demo, superb technology.

[@free_audiobooks]

Qwik will be my next production framework

[@matijacvrk8299]

Loving this approach :) ! Although, as final output gets managed automatically, designing and architecting it as programmers gets hard, because it becomes harder to comprehend. This distancing away from execution is present in any asynchronous programming, so this shouldn't block the progress of such innovation, rather push the programmer tooling as well, perhaps linting or highlighting it in the code editors to signify this, aside of dollar suffix - similar to how promises are expected to be handled in some editors or ESLint/Typescript.

[@roronoa_d_law1075]

12:10 I don't understand, can someone explain this ?

[@MrinmoyRoy1990]

Is this like, it will load super fast, but every click will take a while to do stuff in a slow internet connection?

[@ratoshi21]

it is adressed at 30:00

[@jirkadanek8215]

Actually 34:00, to skip the 4 mins of getting there.

[@ikbo]

Wait so when I click a button for the first time it downloads the code from the server? So it is fast to boot but slow when it actually matters? I don't get how that is an advantage...

[@jonbikaku6133]

Not an expert but what matters is how fast the page delivers to the user and becomes interactive. It has to be easier to download, parse and execute smaller chunks of js when needed, instead of doing it for the whole chunk the second user enters the page.

[@ikbo]

@@jonbikaku6133 I guess that depends on the type of app you have. You could easily argue this would be a downgraded experience in some use cases since going to the network can be expensive. Also designing your client to lazy load is not clear upfront and from the demo there is lot of boilerplate. This is a subpar experience compared to coding in react.

[@DevonWells-j1o]

That's a common misconception. When you click a button for the first time, the button code executes for the first time (and only the necessary code from the listener, doesn't need to actually rerun the entire component or children like React). The code is already downloaded in the background in a service worker extremely fast. Browsers and service workers are extremely good at downloading code (it's all optimized low level C stuff). It's executing the JS that slows things down, and the beauty of Qwik is it only actually executes what's necessary when it's necessary.
In practice, the button interacts instantly in production.

[@meten2137]

Really good talk imo.

[@khalidnawaf1196]

The concept is brilliant and seems remarkably optimized, but it is very complex.
I bet, you spend more money and time on the backend. Just imagine amazon caching all the possibilities of showing suggested items to buy.
Btw, It’s really hard to reason about, thus it would be hard to debug.

[@afoo]

is this something similar to HTMX?

[@IvanKleshnin]

No

[@BewareOfStinger]

I think qwik is smarter than HTMX by the way it uses the service workers. HTMX just uses asynchronous calls to fetch data on click on a button or something. Also HTMX delivers the whole library on startup (although pretty small in size). I'm no expert in both projects so I could be wrong.

[@meten2137]

Not really but I see where the question is coming from

[@edwardharman1153]

Dad-abase :D

[@Taffman91]

Thought it was dada-base :D

[@RoyerAdames]

The issue is that you when with react instead of svelte

[@binarybotany3218]

wow this is awkward