Why Qwik is the Future

[@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.

[@heroe1486]

It's a joke right ? Everyone is complaining about the app directory and how it's unstable, break everything for little benefits and yet is labeled as stable. I don't think devs asked for the app directory or RSCs that are going to mess up the ecosystem, certain features like layouts and SSG + SSR for the same route have been asked for years but probably not in this form. To me it's marketing driven, you have to present "amazing things" during those Apple like "keynotes" after all.

[@mertdr]

@@heroe1486 I’ve been working with app directory for the last few weeks and my overall experience is great so far. At first, it was quite discouraging because I had to find new ways to do things and ditch some of my favorite libraries like react query and trpc. But now I realize why some components should be rendered on server and some on client. Why would I generate certain sections of the content with JS if only things I needed is html, css and data fetching? On the other hand, I agree next13 app dir is not fully ready yet. Especially server actions being in alpha stage. I’ve heard certain caching problems as well yet it might have been resolved with recent releases. Clearly Vercel team realized that Svelte and Astro are coming real fast and they might take over the market soon. That being said, vercel obviously decided to move things forward as fast as possible to maintain their position and this is the result. Naturally it brought problems, especially their approach of pushing people to use app directory (even though it’s still marked as experimental in config file). In my opinion the main problem comes from the presentation and marketing. Also even they can’t easily explain some differences about RSC and RCC. Probably whole transformation will take some time and might be painful but I think it’s a win-win.

[@mfpears]

This has nothing to do with React, it would be a massive breaking change for the React ecosystem, and the React team is far too invested in RSCs to incorporate this, even if they were interested, which they aren't. Which is a separate question from whether it's good, fyi. The React team aren't gods.

[@joohyunglee1815]

@@mertdr I passionately hate how they cache everything

[@jsonkody]

Qwik is light years farther than react and next .. I've just reimplemented my Nextjs app in it and it's really embarassingly better

[@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).

[@artu-hnrq]

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

[@KodapsAcademy]

Thanks for the kind words :)

[@godnyx117]

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!

[@uceumice]

Yeah, it would be the perfect first framework to learn. I would also suggest learning this framework's `behind-the-scenes` to understand what power you are dealing with, to fully utilize framework's function. There is a nearly 3 hour video on this topic, which also covers Qwik City. P.S.: remember to check out other frameworks too ; ) Managing static blog websites is way more easier in Astro. Cross platform requires React and React Native, beyond cross-platform is Dart and emerging Tauri frameworks. Do not limit your horizon, and check out devops on your way up. Cheers!

[@godnyx117]

@@uceumice Tauri seems very promising. I plan to create my own language (compiled) and I'm interested into Tauri for a GUI solution for it. Svelte is also interested, same with Astro. It will take time but I will look a little bit into others and see what I like. Thank you for your time and your suggestions my friend! Wish you to have an amazing day!

[@Mgr1st]

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

[@KodapsAcademy]

I do, thanks for noticing, for pointing it out and for the kind words :)

[@adamwarvergeben]

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

[@KodapsAcademy]

I'm glad you liked it :)

[@atheneus]

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

[@KodapsAcademy]

Thank you very much, that’s so kind :)

[@KodapsAcademy]

Thank you very much, that’s so kind :)

[@jtms1200]

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

[@eli-shulga]

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

[@Dev-Siri]

if qwik splits literally every file/dependency/component/event-listeners/functions/closures/memory/binary/transistor/logic-gates/quantum-mechanics/molecules/atoms/electrons/protons/neutrons into it's own bundle, how does it handle client-side routing? does it lazily load a client-side router when an tag is clicked?

[@gamer-gw9iy]

What

[@KodapsAcademy]

Routing is handled by QwikCity, Qwik’s meta framework, and I believe it preloads SSR pages rather than render them on the client

[@yusril-ihsanul-alim]

The Last Humankind Web Frameworks

[@coders_rant]

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

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

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

[@JohannGarrido]

Priceless video

[@shaunmcdonogh3529]

You did such a great job with this video.

[@KodapsAcademy]

Thanks :)

[@izarrayt]

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

[@KodapsAcademy]

Svelte is more established so it makes sense that there be more jobs for Svelte. Qwik is perhaps better suited to optimizing the JS load of large applications, but Svelte is and excellent choice and may well continue to outperform Qwik in terms of market penetration and jobs.

[@yukendhiran8043]

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 😅

[@ThislsYusuf]

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

[@KodapsAcademy]

No, not as I understand it, the chunking of the JS in Qwik is driven by the compiler and tree-shaking which is not part of streams API. There are similarities between the two though :)

[@hakuna_matata_hakuna]

best tool for the job for buildnig e commerce sites

[@ashimov1970]

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

[@darz_k.]

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

[@KodapsAcademy]

Glad the video was helpful, thanks for your kind words :)

[@unhandledexception1948]

:-0( serializing state of components seems like a flashback to year 2000 (remember asp webforms?)

[@awisemanoncesaid12]

thank you for the great explination .

[@KodapsAcademy]

My pleasure, I’m glad it was helpful :)

[@moutafatin]

Wuw i hate these titles

[@ariell121]

the way this guy speaks about it though...

[@costagmc1]

I think nextjs team will adopt js streaming soon..

[@laughingvampire7555]

the best websites have the least javascript, the problem is our employers want the shiny things like flash ads all over again.

[@welzyalzy]

You are absolutely right.

[@boot-strapper]

I actually dont get why people like nextjs so much. It just seems bad?

[@heroe1486]

Because it was React with a file based router + easy static and server side rendering by exporting a function above your default component. Well it used to be, it's now an entire new framework but minus simplicity and stability

[@AbouAnia]

Qwik is not suitable for an spa…

[@KodapsAcademy]

Absolutely. But Qwik kind of sidesteps that whole SPA paradigm :)

[@Anas_Alaqeel]

Great content but please speak like normal person... chill bro

[@drivebuss8079]

tommorrow a nother one comes and you say it the future!! what a joke!

[@KodapsAcademy]

Did you watch through the video before commenting ? You might find that my position is slightly more nuanced than you make it out to be :)

[@greendsnow]

No it's not. It doesn't have even have proper UI libraries. Don't lie to people, and waste their time. The ecosystem sucks

[@KodapsAcademy]

The problem with trolling is that you end up writing comments that miss the mark. UI librairies and the ecosystem are irrelevant to how Qwik’s implementation might inspire other frameworks

[@heroe1486]

​@@KodapsAcademy Your title doesn't mention "qwik's approach" nor describe the approach but says "qwik". " Tesla is the future" is different from "Electric vehicles are the future". That's the problem with clickbaity/sensational titles, people are more prone to comment without watching, they force reactions. I guess you should just accept that it's a tradeoff of using this strategy, I'd even say those titles are more trollesque than these kind of comments.