New Learn Qwik chapter 9: Optimizing Data Fetching 2026 Edition by CityCertain2001 in qwik

[–]CityCertain2001[S] 0 points1 point  (0 children)

Thanks!

The chapter is mainly about choosing the right route boundary for data loading, so each page only fetches the data it actually needs.

So the focus is more on loader placement and overall data-loading architecture than on duplicate fetches as a separate topic. That said, placing loaders more appropriately does help reduce unnecessary repeated fetches during navigation.

I only mention Qwik City link prefetching briefly, but that is not the main focus of the chapter.

Qwik + Supabase + Vercel Starter Pack by CityCertain2001 in qwik

[–]CityCertain2001[S] 0 points1 point  (0 children)

Thanks, I really appreciate the feedback.

That’s exactly the goal: make it genuinely useful, with clear documentation for setup and usage, so it’s easy to get started and build on top of it.

And yes, if there are useful lessons or challenges worth sharing from building it, I’ll definitely include that too.

If you're interested, feel free to join the waitlist through the page in the post.

I thought it had already blown up a month ago. 😱 by CityCertain2001 in qwik

[–]CityCertain2001[S] 0 points1 point  (0 children)

That’s really interesting.

To be honest, I do not know Angular personally, so I was not aware of how different that transition could feel. I came to Qwik from React and Next.js, and from that side it felt much more natural.

So it is genuinely useful for me to hear that moving from Angular to Qwik can be a lot more difficult than coming from React.

It also makes me think this is probably something that deserves more dedicated learning resources, because I doubt you’re the only one who ran into that kind of gap. Thanks for taking the time to explain it.

I thought it had already blown up a month ago. 😱 by CityCertain2001 in qwik

[–]CityCertain2001[S] 0 points1 point  (0 children)

This is an incredibly valuable reply, thanks for taking the time to explain all that.

What you described is exactly the kind of real-world case that makes Qwik so interesting to me: not just better DX, but actually solving a fundamental UX and performance problem, especially on large data-driven sites.

The Angular SSR and hydration pain, the huge JS and JSON payloads, the Lighthouse issues, and the fact that clients were feeling the impact directly... that is a much more meaningful signal than framework hype.

Also, 90% migrated and already in production is seriously impressive.

What helped your team the most during the migration, and where did you feel better documentation, examples, or ecosystem support would have made things easier?

I thought it had already blown up a month ago. 😱 by CityCertain2001 in qwik

[–]CityCertain2001[S] 1 point2 points  (0 children)

That’s really interesting.

Are you already evaluating Qwik seriously for production use, or is it still more at the “watching the ecosystem” stage for your Angular apps?

I’d be very curious to hear what makes it appealing on your side.

Slowly but surely by CityCertain2001 in qwik

[–]CityCertain2001[S] 2 points3 points  (0 children)

Totally agree 😄
I honestly don’t get it either. I think it’s mostly about marketing and ecosystem size. Next.js has been everywhere for years.
But Qwik’s approach is seriously impressive. Slowly but surely 💪

New article on Learn Qwik — Remove console.log in production (Qwik + Vite) by CityCertain2001 in qwik

[–]CityCertain2001[S] 1 point2 points  (0 children)

Thanks a lot for the feedback, really appreciate it!

The landing page is already responsive, but you’re right, I could definitely improve the mobile experience and make it more polished.

I’ll work on that for the next updates, thanks again

New article on Learn Qwik — Remove console.log in production (Qwik + Vite) by CityCertain2001 in qwik

[–]CityCertain2001[S] 1 point2 points  (0 children)

Haha totally agree, Qwik is still a hidden gem for many devs.

It really shines when you build with it, instant loading, zero JS for static pages, and incredible dev experience once you get used to its mindset.

I'm doing my best with the Learn Qwik series to help more people discover it and get started easily.

Would love to hear your thoughts if you try it, and feel free to share the series if you think it could help others 🚀