Your content is the opposite of Fireship - detailed, crisp, incredibly insightful and thoughtful, and so well-paced and presented. You are a very talented teacher!
Thank you for the kind words. Jeff at @fireship is one of my inspirations, his work ethic and dedication is quite amazing - I do enjoy his short form content a lot actually! I do see a distinct lack of technical content around tooling, that's the void I am trying to fill 🚀 we are lucky to have so many great creators in the software space
Wow it’s awesome to see you and hear you again dude! Great and interesting video and thank you so much for what you do and have done for the community! 🍻
Just do it, don't get too caught up in production quality. Content is king! My early stuff is super rough, you just need to get started somewhere. I'll be your first subscriber 😎@@fadamakis
Can you make a video about how vuejs and reactjs update their state, the difference between them. i tried to find article about this but nothing come up.
I think you are right, I am no expert in this area yet). Maybe not vdom specifically, but it seems the general runtime react/vue ships is pretty huge (well, relative to the solid.js one shown in this video). What else is taking up all those kilobytes if not the runtime (includes the vdom, reactivity, etc). I am still learning how the Svelte/Solid models work, when I find out more I will make a video about it.
@@LachlanMiller Looking forward to that video. I meant it more the other way around. Imo vue has a pretty good compiler and runtime. That's why each component is fairly small. The individual Component code in svelte is larger, with barely any runtime cost. Switching to vapor will remove some kb in the runtime bundle size (the vdom part). I don't think it will affect individual component size much. A recommended read is the webcomponent dev comparison of bundle sizes. all-the-ways-to-make-a-web-component
I have no idea! This is what I mean by NOT FREE - there's a lot of open questions to be answered. Innovation is hard. Looking forward to what doors Vapor mode opens.
Code doesn't just stop working - unless the environment changed, it should be fine. Docker solves this problem! What is the issue, I might be able to help you debug?
"As it is often the case in open source, a mysterious individual with an anime display picture has come along and made a bunch of commits" 😂
Your content is the opposite of Fireship - detailed, crisp, incredibly insightful and thoughtful, and so well-paced and presented. You are a very talented teacher!
Thank you for the kind words. Jeff at @fireship is one of my inspirations, his work ethic and dedication is quite amazing - I do enjoy his short form content a lot actually! I do see a distinct lack of technical content around tooling, that's the void I am trying to fill 🚀 we are lucky to have so many great creators in the software space
Wow it’s awesome to see you and hear you again dude! Great and interesting video and thank you so much for what you do and have done for the community! 🍻
Thanks, I am back on the content creation grind!
Great video. Looking forward to your book about tooling. 👏
Me too. Still have to read the test one… but thats a different story…😢😮😅
Thanks @fadamakis - I still keep up with your content on fadamakis.com. Have you considered making videos? You have a lot of great insights.
@@equinozio22 No rush - I think it'll take a good chunk of 2024 to write this one. I'll send our chapters via email as they are completed.
@@LachlanMiller Thanks! Making videos is a goal I've set again this year, just like last year. 😅
Just do it, don't get too caught up in production quality. Content is king! My early stuff is super rough, you just need to get started somewhere. I'll be your first subscriber 😎@@fadamakis
Your content is so good, looking forward to the book
Thank you for the kind words, this motivates me a lot! Onwards!!!
Can you make a video about how vuejs and reactjs update their state, the difference between them. i tried to find article about this but nothing come up.
Perhaps, I need to learn more first, it's a pretty complex topic (thus no articles!)
I don't think the bundle size is related to vdom. I think it's more about a efficient compiler and clever runtime.
I think you are right, I am no expert in this area yet). Maybe not vdom specifically, but it seems the general runtime react/vue ships is pretty huge (well, relative to the solid.js one shown in this video). What else is taking up all those kilobytes if not the runtime (includes the vdom, reactivity, etc).
I am still learning how the Svelte/Solid models work, when I find out more I will make a video about it.
@@LachlanMiller Looking forward to that video.
I meant it more the other way around. Imo vue has a pretty good compiler and runtime. That's why each component is fairly small.
The individual Component code in svelte is larger, with barely any runtime cost.
Switching to vapor will remove some kb in the runtime bundle size (the vdom part). I don't think it will affect individual component size much.
A recommended read is the webcomponent dev comparison of bundle sizes.
all-the-ways-to-make-a-web-component
Stay tuned, I'll try looking into this in more detail soon!@@grinsk3ks
Excellent video. I wonder, does it affect hydration? Specifically, can it handle content mismatches during hydration, like Vue 3.4 currently does?
I have no idea! This is what I mean by NOT FREE - there's a lot of open questions to be answered. Innovation is hard. Looking forward to what doors Vapor mode opens.
Thanks
awesome video ❤
thanks!
Another useless feature. Vue project built 2 years ago is totally obsolete and doesnt work anymore. Talk about reliability, total failure. Next please
Code doesn't just stop working - unless the environment changed, it should be fine. Docker solves this problem!
What is the issue, I might be able to help you debug?