RIP React? New Qwik Release Is REALLY Interesting

preview_player
Показать описание
I've never been the biggest fan of Qwik. Resumability just didn't seem worth the costs, and the hacks to enable it were...chaos, to say the least.

That said, honestly? Very impressed with what they're cooking here. Excited to try out 2.0 when it drops.

S/O Ph4se0n3 for the awesome edit 🙏
Рекомендации по теме
Комментарии
Автор

I just replaced react with Qwik. I've never been happier.

My homepage is just 8kb, using tailwind, with a complex layout, and loads in 96ms.

jonnyborgesdev
Автор

Qwik also did a great work on eliminating the boundaries between frontend and backend. So much better than Server Actions!

You can define a server only function by wrapping the definition in server$(), then it will only be executed on server side when being called.
And you can define this thing anywhere and call it anywhere. You don't need to use it with an action attribute on form element. And you don't need to worry about 'use client' or 'use server'. The only thing you need is wrapping it inside server$(). And this is just magic!

linkfang
Автор

I'm noticing a recurring pattern in all GUI code: You have one state tree, and another GUI element tree. They're both highly complex, and mostly identical, but different in a some crucial ways. And you're trying to manage a two-way binding between them, which stays reliably in sync at a high frame rate, but without unnecessary re-renders.

andybrice
Автор

Was a fun stream! Qwik has changed a LOT since your last stream with Misko, and really exciting to see a project where a great user experience matches the developer experience out of the box.

thejackshelton
Автор

This is a great breakdown of Quik. I’m impressed with their obsession with performance.

jamonh
Автор

Does every video have to be RIP <something> now?

eldarshamukhamedov
Автор

Not EVERY framework needs binding packages for stuff like popper. All you need is a framework that is friendly towards web components. For example, Angular is (not my favorite framework). I would love a future where every component library supports web components.

zwanzr
Автор

Theo, thanks for keeping us in the loop.

VeaceslavBARBARII
Автор

not game changer, just another js framework

leightonchen
Автор

so what you’re telling me is…Qwik needs another virtual node for that 😅

swanksauce
Автор

Looking at theos shirt gives the same satisfaction levels to my eyes as seeing someone beat the Turkish ice cream man

JC-jzrx
Автор

The first time someone has explained hydration in a way I understand. Now all those hydration errors make sense

callumbirks
Автор

Regarding the tailwind 'vs' qwik complaints: There is two groups, those that care about the semantics of the output (who will dislike qwik and tailwind equally) and those who care about the semantics of the source code.

DavidMulderOne
Автор

idk how I should feel about the 1000th js cool framework out there that I should learn to build a stupid website

fra
Автор

Qwik is awesome but there (for me) is many abstractions... Like I can't just access created element and call native JS functions, for making custom player. I love where Qwik framework is going, but they need to add more air.

realalphas
Автор

I want to build a multi static page site, all static content only not application. Is qwik or astro good for me

jaspervirtual
Автор

The purpose of semantic HTML is to provide correct and precise information to assistive technologies. It's not to make the website source more readable. Tailwind and Quick are just fine in this regard.

nbb
Автор

The way he says attributes is pretty funny

Nerdimo
Автор

The virtual node comments thing seems like a weird hack to me. Why can't resumable nodes just be identified with a unique address stored in a class or a data attribute?

andybrice
Автор

yeah. I both am not very interested in quick as a framework but am very interested with how you cover it here as a tech demo to better understand how code runs. great article by the qwik team!

StefanHayden