Qwik introduction - a framework that goes FAST

A tutorial with some highlights of what I learnt about the Qwik framework from Misko and Giorgio during an in-person workshop in Florence, Italy, organized by the Schrödinger Hat community.

I’ll show some of the main constructs that have been used during the workshop while talking about the framework.

_______________________________
Hit like and subscribe for more content! :D

You can also follow me on the other platforms:
_______________________________
TIMESTAMPS
00:00 Qwik
00:23 Create project
01:00 No Javascript
02:07 Counter Demo
03:45 Resumability Explained
05:00 Alt to Source
05:20 useStore and useTask
07:36 useVisibleTask
08:18 useStylesScoped
09:07 useResource
10:50 useComputed
11:39 useLocation and routeLoader
13:27 useServer
14:45 Contribute to Qwik
15:10 Closing
_______________________________

#qwik #javascript #demo

[DevLeonardo]

Question time! What do you think about Qwik? Are you using it for some personal projects or in production? 👇

[shashydass]

Great video! Qwik is moving fast with features and its awesome to have videos like this tracking the best practices as they evolve. I had forgotten about `useComputed`, will refactor some of my code today!

[martinocom]

That $ reminds me of PHP time and that was bad times ahah

Anyway. I got into React Native programming and re-renders (especially in Lists) are our nightmare. Seeing something new caught my attention, especially when I heard about similarities in React. Then I saw the "$" and I wondered why. I mean, yeah, not everything should be optimized, but for me as a React Dev introduces a heavy "Yet Another Javascript Framework" syndrome, in order to adapt for this new change. Benefits? Yes. But now I need to remember to "dollarify" things, adding up things to remember when doing "react" things.

I heard that react is experimenting in getting rid of useCallback and useMemo in some way, doing it "behind the scenes". And when the big nightmare will go away, being faster will not be the only point qwik should point on. That's IF React Team will do something like this. For now, even a big project that I'm managing right now, feels pretty ok even on lower-end devices. There is no point of getting framework slower, bigger and worse... but is there really a point on getting them "extremely fast" (looking at you, virtual DOM) with "different" syntax?

I'll surely follow updates on this framework, but for now I'll threat is as a "trying to get the best out of React adding $".
Hope to get an answer to change my mind and try it more!

[RolandAyala]

QwikCity is a very exciting and innovative framework that I've prototyped with, and is hands-down is my favorite framework in comparison to SolidStart, Remix, SvelteKit, and Nextjs (listed in order or pref). Qwik solves a lot of problems, and is really well thought out IMO -- the experience of its creators really shines through.

Unfortunately, Qwik suffers from an ecosystem problem (just like Solid and Svelte), and I haven't found the community channels to be very helpful for anything but softball questions (helpful when first getting started, but not so much once get into it) -- this is in stark contrast, for example, to Remix and Solid which have strong communities with deep knowledge experts actively involved, regularly. For example, I recently posted a question to Discord about how Qwikify is working out in production and what are its pitfalls (other than obviously need to bundle/download react) and I received crickets for a response. This is an area Qwik needs to do better IMO, because as an emerging framework, less new features and having knowledge experts actively engaged w/ community to address questions is what's now needed. Hate to be so harsh, but I really want to see Qwik succeed and I don't feel it's on a good path right now. As for Qwikify, this is supposed to be the silver bullet that addresses the ecosystem problem, but I'm dubious it can work well and scale in a real-world production apps and nobody has been able to squelch my concerns. I can only presume the reason is because nobody is using Qwikify, which further exacerbates my concerns so, for now, I'm sticking with React (using Remix).

Great video by the way -- one of the better ones, packed with lots of great info.