Been doing Vue 3.3 for over a month now and I must say it's a great experience. Interesting road map for 2023. One thing that I was hoping to see is some focus on routing - I would love to (more easily) move state into the URL instead of a store like pinia. It make page refresh stable and allows building E2E test jump right into a state/context.
@@faridguzman91 I've literally switched to Vue (tried solid but the ecosystem isn't there yet) from React after years because of NextJS new (unstable) nonsense and React's" you should use a Framework if you build apps with React" statement. Vue was actually my first JS framework but I preferred React back then after trying it, now with Vue 3 + script setup and composables (hooks equivalent) it feels way smoother than it used to.
Been using Vue since 2.1, not really sure, in the early days. And never looked back. With Vue 3.x, the options API is now a thing of the past. Big up to the Vue team. 🎉🎉
Still scratching my head over why JSX is still a thing. Are there any use cases where using it over the regular SFC-template approach has any benefits? I remember specifically and clearly choosing Vue over React because the thought of template logic inside javascript felt hacked together and utterly wrong. Been stuck with Vue-templates (infused with pug notation) ever since.
Some people prefer the versatility of JSX, and you can make JSX less bloated with few components like or like Solid does, even Vue libraries like Vuetify use it. I personally don't mind both, template languages feel cleaner and JSX more powerful and natural since it just feels like JS, but both are ok.
I agree, though one advantage I've heard someone mention were recursive tree structures. You might say you can do this with normal components just fine but it creates more instances of that component.
This is mixing types and JS though which probably breaks some fundemental stuff? It would make more sense to do this: const props = defineProps({ foo: number = 1 }).
amazing, I am using all vue, nuxt and vitepress...haha sounds like a bunch of new features are coming. Indeed, the nuxt virtual dom and actual dom mismatch thing is a bit annoying tho XD
I agree. It seems sort of clumsy. I look at Svelte's syntax and it is so clean and simple. It is a shame they abandoned reactivity transform. Luckily it is being maintain by VueMacros now and you can add it as a plugin.
@@bloodjopa why? It lets you group related lines of code together. It also lets you easily extract shared logic into hooks which is what allows for vueuse to exist - which is easily the best thing to ever happen to the Vue ecosystem. It also lets you write the same code everywhere, both inside Vue components and I plain JS files which is another massive improvement that puts Vue ahead of all other major frameworks. All in all composition API lets you keep big components organized through better code composition. And it lets you share logic that looks and works the same in all contexts. Not to mention that functional programing is where the entire industry is headed. So what's bad about it? I think it's the biggest win I've ever seen in any framework ever
That defineModel macro is such a good upgrade. Much love to the team
Been doing Vue 3.3 for over a month now and I must say it's a great experience. Interesting road map for 2023. One thing that I was hoping to see is some focus on routing - I would love to (more easily) move state into the URL instead of a store like pinia. It make page refresh stable and allows building E2E test jump right into a state/context.
Love vue. easy easy easy, fun fun fun,
In the Vue team I trust. 😊. These guys are good.
I am a react guy but i am thinking of giving vue a try.
please do, we need more vue developers since now react wants the dev monopoly and with nextjs its not going the right direction
You are gonna love it
@@faridguzman91 I will, I didn't like this move.
Same here. Vue seems pretty awesome to me so far.
@@faridguzman91 I've literally switched to Vue (tried solid but the ecosystem isn't there yet) from React after years because of NextJS new (unstable) nonsense and React's" you should use a Framework if you build apps with React" statement. Vue was actually my first JS framework but I preferred React back then after trying it, now with Vue 3 + script setup and composables (hooks equivalent) it feels way smoother than it used to.
Been using Vue since 2.1, not really sure, in the early days. And never looked back. With Vue 3.x, the options API is now a thing of the past. Big up to the Vue team. 🎉🎉
Where can I find the documentation for 9:25 Reactive Props Destructure?
that generic script setup is great, I'm having a hard time upgrading with 3.3.x tho, I'm having some compilation error that doesn't make sense :s.
It has been three years since Vue 3 was released. Why is the Suspense feature still considered experimental?
to keep us in suspense
I was waiting for this video.
Still scratching my head over why JSX is still a thing. Are there any use cases where using it over the regular SFC-template approach has any benefits? I remember specifically and clearly choosing Vue over React because the thought of template logic inside javascript felt hacked together and utterly wrong. Been stuck with Vue-templates (infused with pug notation) ever since.
Some people prefer the versatility of JSX, and you can make JSX less bloated with few components like or like Solid does, even Vue libraries like Vuetify use it. I personally don't mind both, template languages feel cleaner and JSX more powerful and natural since it just feels like JS, but both are ok.
I agree, though one advantage I've heard someone mention were recursive tree structures. You might say you can do this with normal components just fine but it creates more instances of that component.
It means React devs can switch over
11:00 Guys, I think this would be a good approach:
const props = defineProps
This is mixing types and JS though which probably breaks some fundemental stuff? It would make more sense to do this:
const props = defineProps({ foo: number = 1 }).
@@samuelmorkbednarzkepler you’re totally correct.
Vapor Mode will "vaporize" all those Svelte and Solid conceited guys.
amazing, I am using all vue, nuxt and vitepress...haha sounds like a bunch of new features are coming. Indeed, the nuxt virtual dom and actual dom mismatch thing is a bit annoying tho XD
i love all of this
What is Vue's equiiof react server components (RSC)?
Nuxt Server Components
Vue with PHP
great
.value is easy but it's just not honest
I agree. It seems sort of clumsy. I look at Svelte's syntax and it is so clean and simple. It is a shame they abandoned reactivity transform. Luckily it is being maintain by VueMacros now and you can add it as a plugin.
I'm the second one🤩
I am the first one.
It's all about composition api. Not interesting
composition api is awesome
@@samuelmorkbednarzkepler it is not
@@bloodjopa why? It lets you group related lines of code together. It also lets you easily extract shared logic into hooks which is what allows for vueuse to exist - which is easily the best thing to ever happen to the Vue ecosystem. It also lets you write the same code everywhere, both inside Vue components and I plain JS files which is another massive improvement that puts Vue ahead of all other major frameworks.
All in all composition API lets you keep big components organized through better code composition. And it lets you share logic that looks and works the same in all contexts. Not to mention that functional programing is where the entire industry is headed.
So what's bad about it? I think it's the biggest win I've ever seen in any framework ever
Благодарю 👍