Absolutely amazing!!!. By the way Tony, your side comments are nothing less than amazing, you do "big word alert" during the interview casually off the cuff and it really helped me understand what it is about, like for example the explanation of what hydration or serialization is
Tony is the best js instructor . Today i am working on react js because after attending js tutorial on udemy i get really deep understanding of js and my interest in js increases .
Really great to see you Tony active on youtube.. please do more of this and more udemy courses maybe something like a backend lang you are using or Deno or even Bun or whatever :)
Thanks! I am currently adding content to my new early release ES6/ESNext course: www.udemy.com/course/javascript-understanding-es6-and-beyond/?couponCode=6201EAF7BAA446640515
The point you mentioned at the end of the video looks very interesting! Imagine we can take a snapshot of the user app state and debug it somewhere else by a developer. The future looks promising for Qwik, thanks for the video!
Thanks for this! Fantastic stuff. I'm currently brainstorming an integration between Qwik and Xstate, which means I need to understand the internals of both. Your videos are incredibly helpful!
@@TonyAlicea ! i really thank you for "JavaScript: Understanding the Weird Parts" It remains the best course on JavaScript - the "must-watch", the foundation on which any JavaScript learning must be built! After that course, JavaScript became a piece of cake for me. I owe you a great debt of gratitude.
Thanks for the video it was so good ! what a GREAT Mind Miško Hevery have ! how in the world you can think of all this complexity, waw it's so amazing, i understood like 40-60% but it's so good and the impressive stuff is that everything is hidden from the developer, you are just here writing very simple code haha, i hope community start creating UI frameworks and lot of stuff
Thanks Djimi! I like to think of frameworks as complimentary experiments, not competition. React did some important things, and now Qwik is doing some important things. Other frameworks too. And the frameworks we use will continue to improve as they all learn from each other.
Tony, great video, but please clarify a few concepts, and a question regarding Qwik Tutorials. 1) Can Qwik "supplement" existing sites? Or must a site be built purely with Qwik? EXAMPLE: Let's say I have an EXISTING website with ANGULAR 14 as my Front-end, and Golang as my Back-end, does that mean I have to totally scrap that site, and rewrite everything in QWIK? Or, can Qwik be "added" to ANGULAR 14, to help it function faster? 2) Can QWIK be used as a Front-End for a DJANGO website? OR, does that defeat the purpose of QWIK, being both Front & Back-end? Is integration as simple as it would be with, for example Svelte + Django? Lastly: Do you plan to do a "QWIK TUTORIAL" for Beginners? All the short tutorials I've found, seem to only target super-experienced programmers; concepts not well defined. Or, are there any QWIK Tutorial resources?
@@TonyAlicea Hi Tony. I have been looking at their tutorial but i am not seeing where someone totally new to client-side framework can follow. It seems to assume React knowledge and i am not familiar with React. Any suggestions. Great job on HTML&CSS, JavaScript - the weird parts, and NodeJS.
True. For general React-style component learning I would recommend taking a look at the new beta version of the React documentation site, which can be found here: beta.reactjs.org/learn This month I will also be talking a bit more about a possible React course, but that's for the future.
Currently all of my courses are on Udemy, so it is easier to get all student questions in one place. I have considered a Discord for Patreon supporters, however.
I understand the frustration on investing time in new frameworks. Consider though: 1) Let's say a framework only offers "marginal improvements". A series of marginal improvements over time is called "progress". A series of "yet another frameworks" got us from jQuery to where we are now. That doesn't mean you have to use every one that comes out. But continued improvement is a *good thing* as it informs and improves all the frameworks that come out after. It's how we move forward as an industry. 2) I don't think it's fair to call what Qwik is doing as marginal improvements. Right now the JS framework ecosystem is fighting a wall when it comes to performance. Hydration, etc. even have their limits. I think what Qwik is doing (fine-grained lazy loading and resumability) is a very important step forward that both Qwik itself and future frameworks (even iterations of existing ones) will benefit from. The result of that will have tangible benefits, especially for the many many folks in the world that don't have access to fast internet. In the end, the question "is it worth investing the time"...well for you personally, maybe not. Only you can judge that. But for the industry as a whole, absolutely. Eventually we all benefit from the time invested as well.
@@TonyAlicea Fair enough. Well said. One's thing's certain: this isn't the last JS framework. There'll be a new shiny one showing up, adding to more "JS Framework Fatigue". Hopefully, Qwik isn't as confusing to learn as Angular.
@@internet4543 Yeah, I have to agree with you in principle. It's why Blazor and Phoenix Liveview were developed as alternatives to the JS ecosystem, and why Svelte & SvelteKit are gaining recognition.
every framework starts because it improves something significant for some particular use case. if you don't have that problem (like you don't have massive traffic like amazon or eBay have) --- good for you
I’m seeing my teacher for the first time. You have helped a lot Tony 😊. Thank you
Thanks Shrinidhi! I was happy to be on camera for this conversation. Be sure to check out Qwik, it’s really exciting.
Absolutely amazing!!!.
By the way Tony, your side comments are nothing less than amazing, you do "big word alert" during the interview casually off the cuff and it really helped me understand what it is about, like for example the explanation of what hydration or serialization is
Thanks so much, glad it helped!
WoW 🤯Serializing closures 🤯I'm so glad I found this!!! Quik looks awesome.
Is good to see you’re active in RUclips, thanks all the content Tony
You made me love JavaScript. You are one of the best teacher..Thank you
Thanks Gautam! So happy to have been part of your journey!
Tony is the best js instructor . Today i am working on react js because after attending js tutorial on udemy i get really deep understanding of js and my interest in js increases .
Really great to see you Tony active on youtube.. please do more of this and more udemy courses maybe something like a backend lang you are using or Deno or even Bun or whatever :)
Thanks! I am currently adding content to my new early release ES6/ESNext course: www.udemy.com/course/javascript-understanding-es6-and-beyond/?couponCode=6201EAF7BAA446640515
@@TonyAlicea Of course I already got your latest courses! I got the HTML/CSS one! as well. I love your work and big fan of your work overall.
We love you Tony..
You're extraordinary ❤
Thank you!
Looks like Qwik is moving JS frontend framework performance in a good direction. Exciting!
Agreed!
This is amazing stuff! Thanks for the video 😁
Love being part of history being made.
This is really mindblowing...!!!
The point you mentioned at the end of the video looks very interesting!
Imagine we can take a snapshot of the user app state and debug it somewhere else by a developer.
The future looks promising for Qwik, thanks for the video!
Thanks!
Thanks for this! Fantastic stuff. I'm currently brainstorming an integration between Qwik and Xstate, which means I need to understand the internals of both. Your videos are incredibly helpful!
Thanks Amy!
"UNDERSTAND ANGULAR 2.0"
We need that!!!!!
No plans currently, Angular is changing right now with the introduction of signals, but you never know in the future!
@@TonyAlicea Please!!!! Por favor!!!!🙏🙏🙏🙂
@@TonyAlicea ! i really thank you for "JavaScript: Understanding the Weird Parts"
It remains the best course on JavaScript - the "must-watch", the foundation on which any JavaScript learning must be built!
After that course, JavaScript became a piece of cake for me. I owe you a great debt of gratitude.
Thanks for the video it was so good ! what a GREAT Mind Miško Hevery have ! how in the world you can think of all this complexity, waw it's so amazing, i understood like 40-60% but it's so good and the impressive stuff is that everything is hidden from the developer, you are just here writing very simple code haha, i hope community start creating UI frameworks and lot of stuff
Qwik is indeed impressive. It really is something of a dream team of Miško Hevery, Manu Almeida, Adam Bradley, and others.
"resumability is the future" for sure
WOW best teacher and new product
you does Always the best to make awer life better than now you share this framework.
Qwik will destroy react soon
Thanks Djimi! I like to think of frameworks as complimentary experiments, not competition. React did some important things, and now Qwik is doing some important things. Other frameworks too. And the frameworks we use will continue to improve as they all learn from each other.
We want more stuff from you tony please create more courses on css, angular 12, react js , tailwind etc
Tony, great video, but please clarify a few concepts, and a question regarding Qwik Tutorials.
1) Can Qwik "supplement" existing sites? Or must a site be built purely with Qwik?
EXAMPLE: Let's say I have an EXISTING website with ANGULAR 14 as my Front-end, and Golang as my Back-end, does that mean I have to totally scrap that site, and rewrite everything in QWIK? Or, can Qwik be "added" to ANGULAR 14, to help it function faster?
2) Can QWIK be used as a Front-End for a DJANGO website? OR, does that defeat the purpose of QWIK, being both Front & Back-end? Is integration as simple as it would be with, for example Svelte + Django?
Lastly: Do you plan to do a "QWIK TUTORIAL" for Beginners? All the short tutorials I've found, seem to only target super-experienced programmers; concepts not well defined. Or, are there any QWIK Tutorial resources?
to reply to your second question. qwik is a front-end framework
My only question is !! - When are you going to be teaching this framework ?? - QWIK - Under the hood !!
Ha, I'd love to do a Qwik course some day! Meanwhile you can find the Qwik tutorial here: qwik.builder.io/tutorial/welcome/overview.
@@TonyAlicea Hi Tony. I have been looking at their tutorial but i am not seeing where someone totally new to client-side framework can follow. It seems to assume React knowledge and i am not familiar with React. Any suggestions. Great job on HTML&CSS, JavaScript - the weird parts, and NodeJS.
True. For general React-style component learning I would recommend taking a look at the new beta version of the React documentation site, which can be found here: beta.reactjs.org/learn
This month I will also be talking a bit more about a possible React course, but that's for the future.
Can you make a course on java and spring
I don’t have experience with that sadly. Been many years since I’ve written Java.
You should have a discord channel for your students.Discord is good for all the students sharing information.
Currently all of my courses are on Udemy, so it is easier to get all student questions in one place. I have considered a Discord for Patreon supporters, however.
Another revolution by Mishko. I hope this time he will not allow tech giant to f*ck it up like it was with angular.
Yet another JS Framework. Is it seriously worth investing time on this, for what might be marginal improvements? Seriously?
I understand the frustration on investing time in new frameworks. Consider though:
1) Let's say a framework only offers "marginal improvements". A series of marginal improvements over time is called "progress". A series of "yet another frameworks" got us from jQuery to where we are now. That doesn't mean you have to use every one that comes out. But continued improvement is a *good thing* as it informs and improves all the frameworks that come out after. It's how we move forward as an industry.
2) I don't think it's fair to call what Qwik is doing as marginal improvements. Right now the JS framework ecosystem is fighting a wall when it comes to performance. Hydration, etc. even have their limits. I think what Qwik is doing (fine-grained lazy loading and resumability) is a very important step forward that both Qwik itself and future frameworks (even iterations of existing ones) will benefit from. The result of that will have tangible benefits, especially for the many many folks in the world that don't have access to fast internet.
In the end, the question "is it worth investing the time"...well for you personally, maybe not. Only you can judge that. But for the industry as a whole, absolutely. Eventually we all benefit from the time invested as well.
@@TonyAlicea Fair enough. Well said. One's thing's certain: this isn't the last JS framework. There'll be a new shiny one showing up, adding to more "JS Framework Fatigue". Hopefully, Qwik isn't as confusing to learn as Angular.
@@internet4543 Yeah, I have to agree with you in principle. It's why Blazor and Phoenix Liveview were developed as alternatives to the JS ecosystem, and why Svelte & SvelteKit are gaining recognition.
every framework starts because it improves something significant for some particular use case. if you don't have that problem (like you don't have massive traffic like amazon or eBay have) --- good for you