Finally a presentation about that, many people couldn't see the value of this because probably they never worked on a big Vue project, which gets messy quickly with mixins and you don't know where a method is coming from etc. Can't wait for the release
@Anoop PA 1st of all "many" doest not mean "all". Now that this is out of the way, on services, you are not on a vue component context anymore, that's why you have the freaking mixins, which are going away and we get composition API, which will allow us to have services with component "api" style.
Evan is just amazing. Vue is so beautiful and attractive and just good for the soul. This is a "Appreciate it dudes" talk. thanks for uploading the video and to everyone doing great things like we use.
Wow, look how mature Evan's approach is, just think - Vue team is not going to break backward compatibility, this means you will be able to just upgrade and no side effects other than potential performance improvement. This is a real case of progressive enhancement and this is 100% something else what has happened to other js frameworks over the years, when new major releases were released. Good luck, I admire this approach.
What happens if 2 functions are co-dependant of one another, meaning if they are used in the old way in the component, both can access state (this.propName), but in the new way, how would you access data
The requirement of "this" disappears and instead you would use a closure over the shared data. See: github.com/ShetlandJ/Vue3Todo/blob/master/src/hooks/useTodos.js If two features are unrelated but both want to access the same data, are they really unrelated? If so, pass the values into the functions, if not, put them into the same feature ES module
Hope the class syntax gets a reintroduction when it's stable. It solves all these problems and is way more readable for people coming from OO backgrounds.
It is arguable that you could. But realistically there are a lot more jobs on the market for React/Angular. I've personally chosen Vue because I like this framework the most & the learning curve was good. After Vue 3 is released, I think it'll pick up a lot more in popularity within the job market.
Yes, Vue is the easiest out of all of them. Vue steams from Angular, but better. React is something a bit different and Svelte doesn't compare to anything else here. They take a different approach and it's still in it's infancy.
@@thelolladorfking2416 It's not bad, but it doesn't use virtual DOM, so it basically focuses on performance. Which is good, but it's still really really new. I probably wouldn't put it in production at this point. ruclips.net/video/AdNJ3fydeao/видео.html. Svelte is a simple language to learn, but so is vuejs and is more widely used. It's surpassed angular. React is nice too, but it's mostly used for large projects and I would say it's a very niche language. Vuejs offers a good middle ground. VueJs offers other tools which are very useful. A nice CLI, a debugger plugin, unit testing, typescript.
What he said is "ceveat" not "caviar". Yes people (including me) still excited about JS front-end framework, mostly due to the fact that those libraries/frameworks are for to represent the data to user in terms of UI (and UX). WebAssembly is one thing, front-end framework/library is another thing; which they are not to replace one another. AFAIK you can opt-in to use WASM to prepare the data to be shown to the user but without an front-end framework/library you'd go down the dark path - see jQuery for instance. Or better yet use vanilla JS to provide interactivity, you might as well write your SPA with C/C++/Rust.
@@Dylan_thebrand_slayer_Mulveiny This is not code stealing. Vue and react are vastley diffirent. They just share some core consepts. If you think that coding can be reduced to "if you share consepts then you literally stole someones actual code" then you have no idea what you are talking about
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
This guy is so underrated. It's amazing what he's done in a few short years...and his work ethic is legendary.
Vue is one of the most popular frontend frameworks :D, I wouldn't say he's underrated
@Anoop PA Source?
He's a fraud and a liar...keeps pushing back the release date because "reasons" ... he's just milking backers by making promises he can't deliver
@@Dylan_thebrand_slayer_Mulveiny Wtf?! :D :D
Justin L well I gotta say the Vue 3 was said to be coming since 2017 I think
Finally a presentation about that, many people couldn't see the value of this because probably they never worked on a big Vue project, which gets messy quickly with mixins and you don't know where a method is coming from etc. Can't wait for the release
@Anoop PA 1st of all "many" doest not mean "all". Now that this is out of the way, on services, you are not on a vue component context anymore, that's why you have the freaking mixins, which are going away and we get composition API, which will allow us to have services with component "api" style.
Evan is just amazing. Vue is so beautiful and attractive and just good for the soul. This is a "Appreciate it dudes" talk. thanks for uploading the video and to everyone doing great things like we use.
Wow, look how mature Evan's approach is, just think - Vue team is not going to break backward compatibility, this means you will be able to just upgrade and no side effects other than potential performance improvement. This is a real case of progressive enhancement and this is 100% something else what has happened to other js frameworks over the years, when new major releases were released. Good luck, I admire this approach.
Amazing, so good at explaining as well. Looking forward trying out 3.0!
I can't wait for the function based api
I'm using Vuetify. It's a awesome component library. Makes my life as front end developer easier.
Great for understanding the tradeoffs and thought process
When?
I love vue, wish I could use it at work.
same :(
When you worked with it, you'll find some things that you won't appreciate just like whatever you're using today.
@@fire_g i beg to disagree - i work with vue and react and work with vue is a pleasure every time
Tried to learn react and gave it up after a few days, vue is way more easier
Optimized enough to be used as a dependency in an ordinary npm package! Good job!
It's like Half-life, but Vue
The link at the end says "pulls" but it should be "pull":
github.com/vuejs/rfcs/pull/42
Thanks. Let’s Vue make great
What happens if 2 functions are co-dependant of one another, meaning if they are used in the old way in the component, both can access state (this.propName), but in the new way, how would you access data
The requirement of "this" disappears and instead you would use a closure over the shared data. See: github.com/ShetlandJ/Vue3Todo/blob/master/src/hooks/useTodos.js
If two features are unrelated but both want to access the same data, are they really unrelated? If so, pass the values into the functions, if not, put them into the same feature ES module
Are you sure that using Proxy is faster then defineProperty? Because my tests show exactly the opposite.
Hope the class syntax gets a reintroduction when it's stable. It solves all these problems and is way more readable for people coming from OO backgrounds.
Awesome!
I am a beginner and want to learn Vue. Now we all get the basics on Vue 2. Would it be worth to learn Vue ahead of React, Angular or Svelte?
It is arguable that you could. But realistically there are a lot more jobs on the market for React/Angular. I've personally chosen Vue because I like this framework the most & the learning curve was good. After Vue 3 is released, I think it'll pick up a lot more in popularity within the job market.
Yes, Vue is the easiest out of all of them. Vue steams from Angular, but better. React is something a bit different and Svelte doesn't compare to anything else here. They take a different approach and it's still in it's infancy.
@@kungfu71186 I've heard a lot about Svelte in these recent days. What about it?
@@thelolladorfking2416 It's not bad, but it doesn't use virtual DOM, so it basically focuses on performance. Which is good, but it's still really really new. I probably wouldn't put it in production at this point. ruclips.net/video/AdNJ3fydeao/видео.html. Svelte is a simple language to learn, but so is vuejs and is more widely used. It's surpassed angular. React is nice too, but it's mostly used for large projects and I would say it's a very niche language. Vuejs offers a good middle ground. VueJs offers other tools which are very useful. A nice CLI, a debugger plugin, unit testing, typescript.
1:10 so basically NOT LIKE Angular.
touche man. How many projects are in huge trouble due to using one of the first Angular versions
Yeah insanity is clearly a better path. Why fix your framework design mistakes when you can repeat them again. Genius!
Vue FTW
TS is mandatory?
Stop being so lazy
I once heard this. Everyone can learn Vue, Evan You 😂
View has caviar? CaviarJs? Are people still excited about Javascript Front-End frameworks? WebAssembly to Rule them All!
What he said is "ceveat" not "caviar". Yes people (including me) still excited about JS front-end framework, mostly due to the fact that those libraries/frameworks are for to represent the data to user in terms of UI (and UX). WebAssembly is one thing, front-end framework/library is another thing; which they are not to replace one another. AFAIK you can opt-in to use WASM to prepare the data to be shown to the user but without an front-end framework/library you'd go down the dark path - see jQuery for instance. Or better yet use vanilla JS to provide interactivity, you might as well write your SPA with C/C++/Rust.
hello sir please create authentication package for laravel and vue
evan you -> ev-you -> v-you -> vue
So you took the code from react and renamed the variables, genius.
Whats next, vue suspense and you will call it SuspendLoaderVue
This criticism always seemed petty to me. If it works i dont give a fuck where you got it from. Really, who gives a shit?
@@samuelmorkbednarzkepler Uhm, the devs who's code they stole for one?
@@Dylan_thebrand_slayer_Mulveiny This is not code stealing. Vue and react are vastley diffirent. They just share some core consepts. If you think that coding can be reduced to "if you share consepts then you literally stole someones actual code" then you have no idea what you are talking about