Why Qwik is the Future

Let’s take a look at the following questions:
* Why Qwik’s approach is promising.
* How other frameworks have inspired Qwik.
* How Qwik compares to other JavaScript frameworks, particularly React, Next JS, and Solid JS.
* What is the problem Qwik is trying to solve?
but above all: Is Qwik the future of frameworks?

#Qwik #nextjs #reactjs
----------
----------

[mertdr]

NextJS has the upper hand since they’re working together with React team. And it seems like they are open to new technologies, listening developers and adopting these new tech into theirs pretty fast. So nextjs is the way, and apparently Qwik provides a great proposition to move react and nextjs further. Thanks for sharing and explaining the technology behind it.

[RolandAyala]

Excellent assessment and overview of Qwik imho. I've been using Qwik for several months now, and I much prefer it as a framework to React (and Solid, Svelte for that matter). Even though perf / lighthouse is the much stated reason for using Qwik, I find it to be very well-thought-out framework, and the experience of team behind it shines through. The drawback of Qwik (and the others) is, as you point out, ecosystem. It's easy to overlook or dismiss the importance of ecosystem, esp. when chasing shiny new objects, but my productivity takes a nosedive relative compared to React -- lack of tooling, filling in component library gaps, etc. I've gone back and forth between Qwik and React a few times (dilemma between love to use vs. productivity) but keep coming to the same conclusion. Qwik has Qwikify which lets you host React components, but hasn't worked out for me (and generally don't like the idea of needing to add an interop layer anyway).

[godnyx]

I'm learning JS and TS. I don't plan to work for a company (either freelancer or I'll do another job) so, I'm going to learn Qwik right away!

It seems interesting and very modern!

[artu-hnrq]

Good analogies, great visual presentation and well described.
Thanks for the sharing

[adamwarvergeben]

That's a great quality video with even greater explanations, thank you

[jtms]

This is a similar approach to that used by Rails Hotwire or Phoenix Liveview which has been used to great effect for a few years now

[Mgrtimesthree]

Seems like you put great effort into these. Keep going and hope it pays off. :)

[atheneus]

You’re going to hit the 100k subs soon. This is very high quality content

[eli-shulga]

It seems. Qwik may be a solid choice for semi intractable landing pages. Defiantly going to give this a deeper look - Thanks!

[КостяКиндалюк]

5:36 Saying that is assuming everything great initially came with rich ecosystem and thousands of those who learned it before it was released

[ThislsYusuf]

JS streaming is an innovative concept. Is this the same as Streams API?

[Dev-Siri]

if qwik splits literally every into it's own bundle, how does it handle client-side routing? does it lazily load a client-side router when an <a> tag is clicked?

[hakuna_matata_hakuna]

best tool for the job for buildnig e commerce sites

[shaunmcdonogh]

You did such a great job with this video.

[izarrayt]

Better than Svelete, would you say? The thing is the jobs available for that framework

[coders_rant]

That explanation and visual representation on SSR was great! Make MORE!!!

[darz_k.]

Quality piece of production work in this video, and really useful information.
Cheerz.

[yukendhiran]

Nextjs is in version 13.5 and qwick is in version 1, wait qwick to grow it will have rich eco system

And wait for nextjs 14 they will implement this concept 😅

[costagmc]

I think nextjs team will adopt js streaming soon..

[ashimov]

Help! I am completely lost in this new emergent front end tech landscape! How does HTMX compare with or augment Qwik???!