Thanks for the share !

Share the code PLEASE !

SSX is a good game! I used to play SSX on Tour in my golden years,

Thanks

whats the vscode theme? look great

24:00 Instead of the JSON.stringify I’d recommend looking into the defineModel macro. This macro was released with Vue3.4 in december 2023. Which would’ve been around the time this conference was recorded. Which is probably why this wasn’t included in this talk.

8:41

Vue with You.

Just to point out. The most ugly thing done bad in vue3 is refs which reference the dom. I got no idea why evan made it so bad, whereas the perfect solution was so obvious -- just introduce $ref() for dom refs. Why? const foo = ref(null). What is foo at runtime? A number? Boolean? Collection? U never know. U need to check the template part to be sure. And if that's a dom element, u now can't use the name 'foo' coz it's reserved coz of the ref name. Looks like bs. A proper implementation would be: const notFoo = $ref('foo') const foo = ref(1) Now i see that notFoo is a dom reference, which references a ref=foo element, moreover that attribute doesn't pollute my code (doesn't restrict me from naming smth foo in my code) It seems like evan was drunk while he was implementing dom refs in vue3

Give John a boonie hat and cigar, and he just looks like "captain john price" from COD

I use reactive like const state = reactive({ thing1: ‘defaultValue’, thing2: -1 )}; In other words, I use it to group state together. Don’t show me 10 lines of individual refs for a small form, just make a reactive formState object.

I'm jealous of what your company is moving to! My company is stuck with a monolith for now :(

20:37 - "Hydration mismatch" - even in a single file tutorial example 😅 If a developer can make a mistake so easily, it means there is something wrong with the platform itself. Meanwhile, Vue.js developers still can't stop smiling in all their videos, feigning happiness 😂 "This is fine" 🔥🐶🔥

"Can anybody tell me what is wrong with this code?" "Yes: Vue.js!" 😏

Wow, you’re amazing! How can I be as incredible as you?

Great video, thanks! Wish I saw this 2 years ago. Personally I wish I could just mutate props, OR create a new 'v-model' style thing or prop alternative that works both ways. It would make most of the simple stuff syncing between parent/child quicker and easier. Quicker and easier is the whole point of reactive stuff in the first place! The defineModel() is almost that. Now I just bung most data in a composable or Pinia store anyway so it syncs globally...

awesome🎉

Thanks, amazing content

Amazing presentation. Very impressive. Very very well presented!

Great talk Adam, thanks for sharing your experience!

In that last mutating props example, wouldn't _data be initialized only once, so once u pass that object up to the parent (and the parent doesn't clone it), you'll end up still mutating the same object? 23:59

Great talk especially the "Preserve Object" pattern. I don't think I've ever seen this question broached before so… thank you!

terribly slow lecture 😞

When does prop drilling become too much? In the example Michael used there was a three-level hierarchy of components. Do we consider this prop drilling big enough so that we need to replace it by the Data Store Pattern, which also adds other complexities? Can anyone share own experience, as I'd like to explore different point of views

I am postponing migrating a middle size project from vuex to pinia. This video gave me a boost.

for students

Fantastic talk, have never thought of doing the bridge for both, going to suggest it in work when I get the chance 👍

second comment

'promo sm' 👉

It may be worthwhile to note that Living Pages Research in 2000 did the exact same thing with the FormsX library. Except with <FormsKit> replaced by <applet>. It was the pre AJAX era ;)

Totall basics. nothing interesting

I liked the pattern that eliminates prop drilling, but I can’t help to think it would be a nightmare combining it with Storybook

I wish I had more hours in my day to work within Vue 3. Recently I've been focused on all things VitePress, and loving every minute of it - thanks for such excellent work to everyone involved! 🏆

Nice 👍

I'm too lazy to read the documentation, a very useful video, I learned everything I need from here, thank you

Great talk ! i love it ! Is it possible to have more examples or a git repo ?

Thanks a lot

I still haven't forgiven you for breaking Vue 2 so bad with Vue 3. I really don't want to use it after the messup.

is cloning the object will make some performance issues if the object is complex or have function properties ?

Thanks a lot for having me 💚🙏 Any questions left? Let me know below! 🙌

> vite has evolved from just a dev server to something that is much more significant. I agree, it's the new core-js.

Evan, I think it's important that you physically make it to these events. I know Toronto is a long way from home but most of a conference is about connecting and that just doesn't happen over a video feed. Secondarily physical proximity produces accountability and focus on preparation that doesn't happen (as well intentioned as you are). The kickoff to this presentation was awkward, a primary focus on the past -- while intellectually interesting -- is not a good way to encourage excitement in the community. You're an amazing individual and a great presenter but this presentation was not up to your standard nor does it show a firm commitment to VueJS and encourages the idea that your focus has shifted to the larger ViteJS playing field. I still firmly believe VueJS is a 1st class SPA framework and still my favorite but effort needs to be made to stay relevant (when your name is not pronounced "React" and you're no longer the coolest kid on the block). I do get that as the SPA space matures, it's harder to be "sexy" in the change that's released but basic blocking and tackling needs to be executed on (which includes physical attendance of events). COVID made us all get used to work from home but also enabled lazy behavior (the latter we can't continue as we move forward). I don't know nearly enough about your day to day to say you're lack of attendance was lazy (my guess is it was not) but I will say with confidence that this year's talk was delivered with less enthusiasm and apparent preparation than those in the past. Your voice only sounded excited when you switched to ViteJS and IMHO the only emphasis ViteJS should get in a VueJS conference is how Vue integrates with it. I love ViteJS but it is a cross-platform tool and it's scope causes more problems than it solves.

Great to get some insights & learnings of the Vue 2 to Vue 3 transition. 🙌

I am wondering if you are going to post the other talks. I gave a lightening talk and I'd love to have it for reference.

Love the refactoring tactics.

I can't run npm install after clone the example repo. it seem's something wrong.

vee validate docs are so poor

What about defineProps, would you duplicate defineProps per logic? Or, just put it blow imports?

voice is comming from left channel only :(

React is the better, React is best