And becoming bloated with many different ways to solve one problem because of the initial flaw in the design. While also making people pay to learn their framework because there is no documentation of the new version.
AnJ Andrzej I would not say that they are becoming bloated. These features are purely additive and is the underlying logic that they are using anyways, so you are pretty much just getting more access and control over what you have been using vue for all this time anyways. Bloated would infer that it will make your applications slower or give you bigger bundle sizes, but from I have heard von Evan You's presentation of Vue 3.0 is that it is actually going to be faster and he did not mention anything about bundle sizes so I suppose it will still be super light weight. Since Vue 3.0 is still in development it is obvious that there is not any official documentation out yet, but from what we have seen before, Vue has got pretty much the best documentation of all the frameworks so I am sure they are working on new one right this moment!
@@daniellionel01 even if they are purely additive people will be forced to get familiar with it. This is because other people will use it in their code and everyone at some point stumbles across other people's code. More ways to do things is making language harder to learn and sets entry bar higher. Even if each and every way is simple by itself pure number of solutions make it harder.
@@anj000 I don't blame anybody for feeling frustrated with these or ANY new changes to this or ANY framework. But I also personally don't believe that a single or team of framework authors can predict the future, and therefore new concepts arrive years after initial creation of said framework. I hope that people don't think that Vue, since its creation in 2013, first release in 2014, could have prevented this kind of an addition. 5-6 years later. That is a very long time. As for paying for the learning, I believe that many people might have similar feelings. But there already are some (conference videos, blog posts) and will be many more, free learning resources. Vue has temporary documentation for it one a separate site at vue-composition-api-rfc.netlify.com/, and for sure they'll have things in place once the v3 is public (early 2020 maybe). It's well known that Christ Fritz and many others do a really nice job at documentation . I see your point about people "Being forced" to use the new style. Though I do feel a bit differently, I do agree with the sentiment that things "might" lean that way in the coming 2 years as it becomes a better practice. I find that there are always many ways to skin a cat or program things, even if using a strict toolkit. I've found that since my days writing ActionScript 3 with Flash, with Vanilla JavaScript in 2003+, with jQuery even, etc. And yes, I've felt my share of either A) annoyance or even B) fear at having to learn a new way. But if I never did things differently, I'd be creating interactions with Flash (full support and distribution is done as of December 2020), and would never have really pursued advanced open web/JS stuff, or even Vue for that matter. FWIW, I'm thankful that the Vue team responses well with the community's outspoken reaction to the previous to the previous (now defunct) API, the Function API, and subsequently created the Composition API. In another world, another time, etc., a team may not have paid attention to folks and we'd be stuck with a less elegant solution/change.
@@anj000 i love vue and i am glad there is a good alternative to angular and react but this new composition api is a direct copy of react hooks and feels like more over-engineered JS
I've been using Composition API for some weeks now and it's truly adicitve. The code gets so clean and reusable. At first it all seem confusing and not understanding the advantages but quickly start loving it and now won't be going back.
@@gustavopetersen2256 Believe me, this is way more organized. The more I use, the more I see the potential, and I'm just scratching it. It's starting to come out more content and examples, have a look here: ruclips.net/video/-Aoyja_BjZY/видео.html
I am so glad I started looking at VueJS to solve my front-end development challenges. Seeing this video about the Vue 3 Composition API makes it clear to me this is the right direction for me as a beginner in Vue. I've been fighting rebinding problems after ajax calls in my jQuery and native JS applications and have been thinking more and more about (and planning) for production ready code rather than my garbage ways for so long. I appreciate how you put these videos together and look forward to seeing more from you. Thank you so much.
How are using composition functions that different to using mixins or mixin factories? They seem to have similar downfalls and your presentation ends before you have addressed this?
Composables and mixins have completely different pros and cons...Mixins are pretty restrictive and difficult to work with when you have a few in your project in comparison to composables which tend to operate pretty effectively as independent modules and scale far better than mixins.
I swear to my neighbor's cat, the way Vue Mastery instructors explain things, it's very easy to understand, with their simple examples, breaking topics to a smaller topics, how I wish all instructors are like them the world would be a better place
Composition functions tell the IDE everything they need to know right in the function signature, specifically, their return type (ie, it'll know a composition function yields reactive properties X, Y and Z). All these reactive objects, methods, etc are composed and returned by setup(), and *those* objects are then inserted right in the template. Since there's a clear relationship of what object came from what place, the IDE has all the information required to allow autocomplete, hover info, linting, type checking and even refactoring such as renaming. Previously, we needed to do some weird hacks and workarounds to allow typing the `this` object in Vue based on different options that follow different structures (just look at how we type props or computed properties in Vue 2). The composition API drops `this` altogether and relies on explicit references to real objects.
@@rallokkcaz React hooks is called every render so the sequence to call hook function is restricted. Same reason cannot call hooks in condition branch. Also react lacks a reactive system like vue, so useEffect and useMemo must attach a dependency list. You should also notice that every time you call useState the state you got is just fixed at the time render function is called, so you must pay attention to pass them in async function, while in vue the reactive system make every reactive var is up to date. By the way the react is less efficient than vue coz every render create new closures while in vue closure only created once.
@@tianhaofang5419 what you are saying can be done in react by using a class based component without hooks. Hooks allow you to make you view and effect a result of your props and state for only their values within the current render.
At 5:15 you say we need to look inside each factory to know what it exposes but it's exactly the same with composition API... I mean, when you start importing stuff, it's just logical that you need to go in the imported file to know what's inside, that's not a not a con, that's just normal.
In my oppinion Vue 3 generate more problems, tham solve. Also it was Vue feature across frameworks: simplicity. And on high level React still will be so much better than Vue 3.
I've got a question, how is it the right way to write the composables? Create a single file for each action or function or one that could contain different functions and then import from components only the needed ?
Excellent explanation Gregg, and good job selling the reasons why Vue 3.0 is an improvement in several areas. Hopefully your series will reduce the fear of updating legacy Vue 2x apps that some of us have.
Oh this is great for sharing functionality between components. I was looking for something like this. As a workaround i was creating new prototype functions the vue object in main.js.
We do! This is the first lesson and the second one is here: www.vuemastery.com/courses/vue-3-essentials/setup-and-reactive-references We'll be releasing new lessons regularly, which you can watch if you become a subscriber over at VueMastery.com
I really need to try learning this when I get time. I know how to use Vue 2, but this composition API looks awesome. And yeah, the fact that it's more vanilla than Vue 2 and more flexible is nice.
The is why I feel Angular is the best. - Functionalities are broken up into services and can be used by any component. Plus components are broken up into separate files, so the JS and the template are in it's own files, so it's super readable and clean. - Write everything in TypeScript (so everything is strongly typed and prevents errors) Angular may have a higher learning curve, but it's worth it.
I look forward to this feature, reusing logic using mixins worked okayish, using slots was hard to read for others that did not write the initial code or even for yourself after few weeks 😄
I cannot find any references on the VueJS website talking about the Vue 3 composition API. Is this video only talking about what is coming, but not here yet for a stable release?
@@VueMastery so in other words, I was trying to learn what I thought was current and wasting my time. I will check it out, but do we have possible release date?
It does seem odd to me that javascript frameworks, Vue included , never talk about solving real world programming problems, but only about theoretical issues that you can run into if you don't pay attention. If your argument start with "things get messy when your component becomes large" then your solution should probably be dividing the component into smaller parts, not to restructure your entire framework to convince users to write the same amount of code in a slightly less messy way. I get the same feeling with hooks, when the argument is that the code that *calls* the hookis more readable because there are fewer lines. They never talk about the fact that you have to look into the hookcode to see what it's doing; you can nolonger see that from the code that calls it,and you can not just not modify the hook because that might break it's usages. Pretty much al of these problems have been solved long ago in existing frameworks, why does javascript pretend to have to re-invent the wheel? Is this just because Javacript is not a very usefull langauge (you write the entire framework in a transpiler; Typescript, that should be an indication that javascript is crap, right?)
about the first limitaion. as soon as you component start to grow and do a lot of stuff. this is the time you need to split it across couple of components(because you probably do a lot stuff in one component instead of Single responsibility principle [like with react]). also it's dosn't really matter if you do all the dirty job in setup func or across data/methods..... its still gonna looks ugly. and in my opnion setup will looks much more ugly because you actually mix couple of logics in one place. so about the first limitation the compo api not really solved that. and the example of search input you showen here. the logic and code of sort should not be in search component. and in big projects you probably have vuex to manage the search and sort and the components not doing too much. and about the mixing problem you right mixing isnt really flexiable bug still compo not really solved that. and belive me i build a really bigs projects in vue and the compo api its nice but not really solved the problems. and if i can say the idea of methods/data... really remind me the idea of mvc (its not mvc at all but the idea of split the logics each one to correspond place) and the compo api break it
You need to try it first. You also split the logic and that logic can be reused in different components. Give it a go and you'll love it when you start getting the idea.
Vue 3 is quite a disappointment. They spoiled once clean and efficient framework into a messy behemoth. Fail. They call object way of separating things a mess, butt actually this was elegant and clean while Composition api is a mess. Perpetual changing of rules means that you actually don't know what you are doing. Compare that urge for an infinite rewrite to ancient but still elegant C. It has not changed with time, because it was written brilliantly from the start. Those new languages are mostly a gimmick, not really efficient tools.
Looks like Vue 3 is slowly adopting and becoming React, which is expected since these frameworks move towards the same direction and have to evolve to get better on each iteration. Once WebComponents become streamlined none of these will matter.
Sorry but starting the video saying that Vue comps become unreadable and less maintainable when they get bigger as a confirmation so React and Angular comps are real mess in the same situation otherwise beginners will think only Vue have this issue and I do not agree on the Typescript limitations point. And btw all of them are fine to me, it's all about how far you go with your atomic architecture design and where to set the comp logic either locally or globally depending on the feature. Good demo though ;)
I think VueMastery has got a good concept but the explanations are suited for people who have years of experience using vue or react. They fail miserably with true beginners. Videos tutorials should enhance the comprehensibility of the documentation; in this case, for instance, understanding Vuex is a lot simpler in the docs, than watching the whole course about Vuex on vueMastery.
Whats wrong with using OOP in your app instead of trying to reinvent the wheel? Just make an order and sorting object or an ResultSet Object which has these methods. This problem vue tries to fix can be easy fixed with OOP.
they aren't making it anymore complicated to make an app with vue they are just adding another way for the people that want to use it. This new api is very useful for bigger apps. But when you're learning you don't have to use this new api. As a person who like typescript I am also happy they are making this change since there will be better typescript support with it.So this isn't exactly why angular failed. Angular failed because they completely rewrote the entire framework changing the syntax and everything without any warning and no backwards compatibility.
@@johanw2267 seriously the worst answer you can give, you sound like just another youtuber chilling his opinion without even working day by day with it in a very big project. :D
if you want to reuse code and have a clean project structure, then use Angular , not Vue :D ... just funny this composition api, nothing special .. same mess in Vue... i would never use vue for my personal projects
MESSINS :) You did it all wrong at the first place and now is fixing it in another wrong way. Your framework is conceptually wrong that's why you struggle with everything.
This is what I love about Vue so much: it's fresh, simple, and grows by looking back on itself and the industry around it! good stuff
And becoming bloated with many different ways to solve one problem because of the initial flaw in the design.
While also making people pay to learn their framework because there is no documentation of the new version.
AnJ Andrzej I would not say that they are becoming bloated. These features are purely additive and is the underlying logic that they are using anyways, so you are pretty much just getting more access and control over what you have been using vue for all this time anyways. Bloated would infer that it will make your applications slower or give you bigger bundle sizes, but from I have heard von Evan You's presentation of Vue 3.0 is that it is actually going to be faster and he did not mention anything about bundle sizes so I suppose it will still be super light weight. Since Vue 3.0 is still in development it is obvious that there is not any official documentation out yet, but from what we have seen before, Vue has got pretty much the best documentation of all the frameworks so I am sure they are working on new one right this moment!
@@daniellionel01 even if they are purely additive people will be forced to get familiar with it. This is because other people will use it in their code and everyone at some point stumbles across other people's code.
More ways to do things is making language harder to learn and sets entry bar higher. Even if each and every way is simple by itself pure number of solutions make it harder.
@@anj000 I don't blame anybody for feeling frustrated with these or ANY new changes to this or ANY framework. But I also personally don't believe that a single or team of framework authors can predict the future, and therefore new concepts arrive years after initial creation of said framework. I hope that people don't think that Vue, since its creation in 2013, first release in 2014, could have prevented this kind of an addition. 5-6 years later. That is a very long time.
As for paying for the learning, I believe that many people might have similar feelings. But there already are some (conference videos, blog posts) and will be many more, free learning resources. Vue has temporary documentation for it one a separate site at vue-composition-api-rfc.netlify.com/, and for sure they'll have things in place once the v3 is public (early 2020 maybe). It's well known that Christ Fritz and many others do a really nice job at documentation .
I see your point about people "Being forced" to use the new style. Though I do feel a bit differently, I do agree with the sentiment that things "might" lean that way in the coming 2 years as it becomes a better practice.
I find that there are always many ways to skin a cat or program things, even if using a strict toolkit. I've found that since my days writing ActionScript 3 with Flash, with Vanilla JavaScript in 2003+, with jQuery even, etc. And yes, I've felt my share of either A) annoyance or even B) fear at having to learn a new way. But if I never did things differently, I'd be creating interactions with Flash (full support and distribution is done as of December 2020), and would never have really pursued advanced open web/JS stuff, or even Vue for that matter.
FWIW, I'm thankful that the Vue team responses well with the community's outspoken reaction to the previous to the previous (now defunct) API, the Function API, and subsequently created the Composition API. In another world, another time, etc., a team may not have paid attention to folks and we'd be stuck with a less elegant solution/change.
@@anj000 i love vue and i am glad there is a good alternative to angular and react but this new composition api is a direct copy of react hooks and feels like more over-engineered JS
I've been using Composition API for some weeks now and it's truly adicitve.
The code gets so clean and reusable.
At first it all seem confusing and not understanding the advantages but quickly start loving it and now won't be going back.
@Lukas Kreutzer You use this plugin for Vue 2
github.com/vuejs/composition-api
im in that "not understanding the advantages". Probably due to not real examples, ill look deeper
the "old" approach can be messy on big apps, but they can grow in a organized way...
@@gustavopetersen2256 Believe me, this is way more organized.
The more I use, the more I see the potential, and I'm just scratching it.
It's starting to come out more content and examples, have a look here:
ruclips.net/video/-Aoyja_BjZY/видео.html
@@gustavopetersen2256 check Academind channel video about vue 3... he is very articulate and showed and explained it quiet well...
I am so glad I started looking at VueJS to solve my front-end development challenges. Seeing this video about the Vue 3 Composition API makes it clear to me this is the right direction for me as a beginner in Vue. I've been fighting rebinding problems after ajax calls in my jQuery and native JS applications and have been thinking more and more about (and planning) for production ready code rather than my garbage ways for so long. I appreciate how you put these videos together and look forward to seeing more from you. Thank you so much.
The only thing is people always forget to change the favicon, so research presentation pages have the vue icon at the top 🤤
How are using composition functions that different to using mixins or mixin factories? They seem to have similar downfalls and your presentation ends before you have addressed this?
Composables and mixins have completely different pros and cons...Mixins are pretty restrictive and difficult to work with when you have a few in your project in comparison to composables which tend to operate pretty effectively as independent modules and scale far better than mixins.
Excellent, short and concise! Like the part you are showing the disadvantages of older syntax.
I swear to my neighbor's cat, the way Vue Mastery instructors explain things, it's very easy to understand, with their simple examples, breaking topics to a smaller topics, how I wish all instructors are like them the world would be a better place
What's with the cat tho lol
I really love Vue 3 and the new composition api. Using Vuex less thanks to composables. Also you not limited to use one root element in the vue files.
Great video. It's just missing the last part promised at the start. The TS support. How does the Composition API support TS better?
Composition functions tell the IDE everything they need to know right in the function signature, specifically, their return type (ie, it'll know a composition function yields reactive properties X, Y and Z). All these reactive objects, methods, etc are composed and returned by setup(), and *those* objects are then inserted right in the template.
Since there's a clear relationship of what object came from what place, the IDE has all the information required to allow autocomplete, hover info, linting, type checking and even refactoring such as renaming.
Previously, we needed to do some weird hacks and workarounds to allow typing the `this` object in Vue based on different options that follow different structures (just look at how we type props or computed properties in Vue 2). The composition API drops `this` altogether and relies on explicit references to real objects.
This is just right on point and clean. GREAT! Not even Evan could explain it like that, he still got beginners confused, you did a better job.
"They are called useSearch and useSorting"... Where have I seen this naming convention before... 🤔
It comes from react hook but is far better, coz using hook brings many restrictions.
Tianhao Fang what restrictions?
@@rallokkcaz You can't call hooks inside of conditional blocks as React is using an internal array to keep track of the hooks, for example.
@@rallokkcaz React hooks is called every render so the sequence to call hook function is restricted. Same reason cannot call hooks in condition branch. Also react lacks a reactive system like vue, so useEffect and useMemo must attach a dependency list. You should also notice that every time you call useState the state you got is just fixed at the time render function is called, so you must pay attention to pass them in async function, while in vue the reactive system make every reactive var is up to date. By the way the react is less efficient than vue coz every render create new closures while in vue closure only created once.
@@tianhaofang5419 what you are saying can be done in react by using a class based component without hooks. Hooks allow you to make you view and effect a result of your props and state for only their values within the current render.
At 5:15 you say we need to look inside each factory to know what it exposes but it's exactly the same with composition API... I mean, when you start importing stuff, it's just logical that you need to go in the imported file to know what's inside, that's not a not a con, that's just normal.
Thanks for that perfect explanation, that's the why is Vue.js is the best 👏
Can I think of this like php traits? Because that's what the names useSearching and useSorting remind me of.
In my oppinion Vue 3 generate more problems, tham solve. Also it was Vue feature across frameworks: simplicity. And on high level React still will be so much better than Vue 3.
Great videos! However I'm wondering why you are using spread operator with functions in 3:00
I've got a question, how is it the right way to write the composables? Create a single file for each action or function or one that could contain different functions and then import from components only the needed ?
Fantastic!! I love Angular and React but I also love Vue!! Is so simple and adaptable!!
Excellent explanation Gregg, and good job selling the reasons why Vue 3.0 is an improvement in several areas. Hopefully your series will reduce the fear of updating legacy Vue 2x apps that some of us have.
Oh this is great for sharing functionality between components. I was looking for something like this. As a workaround i was creating new prototype functions the vue object in main.js.
do you have a full vue 3 course somewhere?
We do! This is the first lesson and the second one is here: www.vuemastery.com/courses/vue-3-essentials/setup-and-reactive-references
We'll be releasing new lessons regularly, which you can watch if you become a subscriber over at VueMastery.com
@@VueMastery I see now vue 3 isn't really ready for production. Would love to see vue 3 + nuxt soon
@@whatthefunction9140 You can use it by install vue-composition-api npm package in Vue 2.5. now I cannot leave it!
@@tianhaofang5419 this is good to know. I can tell this is going to be the future.
does anyone have an example of the mixin factory ? Thanks
Amazing explanation! How did you make that smooth and sleek animation on the video? Would you like to share what software to made a video like that?
Oh I miss Greg and the Code School way of teaching. Pluralsight may have bought out Code School, but the methodology lives on!!! :)
I really need to try learning this when I get time. I know how to use Vue 2, but this composition API looks awesome.
And yeah, the fact that it's more vanilla than Vue 2 and more flexible is nice.
you might like react (with hooks)
click video, realize it's Greg, all the memories of Rails 4 Zombies wash over me
To me the memory of Greg is Angular 1.x :)
His T-Shirt color is one of my favorite colors.
The is why I feel Angular is the best.
- Functionalities are broken up into services and can be used by any component.
Plus components are broken up into separate files, so the JS and the template are in it's own files, so it's super readable and clean.
- Write everything in TypeScript (so everything is strongly typed and prevents errors)
Angular may have a higher learning curve, but it's worth it.
If you prefer the class based API when declaring components with typescript. Well check this out :)
vuejs.org/v2/guide/typescript.html
Separation of concern is different with file separation ;)
I look forward to this feature, reusing logic using mixins worked okayish, using slots was hard to read for others that did not write the initial code or even for yourself after few weeks 😄
Also, I look forward to your course:)
I Love Vue.js
This cleared up so much for me
Is it safe to use the vue composition api in its current state? Is it going to be the same when Vue3 comes out?
People who do these courses do know there are Class based Vue users right?
Wow you are an amazing teacher!!!
I cannot find any references on the VueJS website talking about the Vue 3 composition API. Is this video only talking about what is coming, but not here yet for a stable release?
It's still a work in progress. Check this out => vue-composition-api-rfc.netlify.com/
@@VueMastery so in other words, I was trying to learn what I thought was current and wasting my time. I will check it out, but do we have possible release date?
Anyone? Is the '...' in front of useSearch() the spread operator? or just bad graphics? If spread, what does it do here?
Hi Gregg, 2 years after you introduced Composition API, Nuxt 3 is STILL NOT THERE.
Thank you guys.
Good presentation approach ! Motion-graphics ?
thats neat... i prefer this type of layout...
It does seem odd to me that javascript frameworks, Vue included , never talk about solving real world programming problems, but only about theoretical issues that you can run into if you don't pay attention. If your argument start with "things get messy when your component becomes large" then your solution should probably be dividing the component into smaller parts, not to restructure your entire framework to convince users to write the same amount of code in a slightly less messy way.
I get the same feeling with hooks, when the argument is that the code that *calls* the hookis more readable because there are fewer lines. They never talk about the fact that you have to look into the hookcode to see what it's doing; you can nolonger see that from the code that calls it,and you can not just not modify the hook because that might break it's usages.
Pretty much al of these problems have been solved long ago in existing frameworks, why does javascript pretend to have to re-invent the wheel? Is this just because Javacript is not a very usefull langauge (you write the entire framework in a transpiler; Typescript, that should be an indication that javascript is crap, right?)
Tests are important and much easier to do with fewer combined concerns
What are you saying man lol you are USING JavaScript in TypeScript
about the first limitaion. as soon as you component start to grow and do a lot of stuff. this is the time you need to split it across couple of components(because you probably do a lot stuff in one component instead of Single responsibility principle [like with react]). also it's dosn't really matter if you do all the dirty job in setup func or across data/methods..... its still gonna looks ugly. and in my opnion setup will looks much more ugly because you actually mix couple of logics in one place. so about the first limitation the compo api not really solved that. and the example of search input you showen here. the logic and code of sort should not be in search component. and in big projects you probably have vuex to manage the search and sort and the components not doing too much. and about the mixing problem you right mixing isnt really flexiable bug still compo not really solved that. and belive me i build a really bigs projects in vue and the compo api its nice but not really solved the problems. and if i can say the idea of methods/data... really remind me the idea of mvc (its not mvc at all but the idea of split the logics each one to correspond place) and the compo api break it
You need to try it first.
You also split the logic and that logic can be reused in different components.
Give it a go and you'll love it when you start getting the idea.
You tutorials are fantastic!! The visual animations, coupled with clear explanations, and simple examples, are what really standout!!
What software do you use for editing?
Keynote and Adobe Premiere
so amazing
nice explanation, :)
Vue 3 is quite a disappointment. They spoiled once clean and efficient framework into a messy behemoth. Fail. They call object way of separating things a mess, butt actually this was elegant and clean while Composition api is a mess. Perpetual changing of rules means that you actually don't know what you are doing. Compare that urge for an infinite rewrite to ancient but still elegant C. It has not changed with time, because it was written brilliantly from the start. Those new languages are mostly a gimmick, not really efficient tools.
I love the sass at 2:35 "And the answer here is no" 😂
Am still waiting to see vue on it's own without relying on react to do anything. That will be very nice.
A good teaser to what's coming up in vuetoronto.com. Gregg, are you coming this year too?
good explanation
Looks like Vue 3 is slowly adopting and becoming React, which is expected since these frameworks move towards the same direction and have to evolve to get better on each iteration. Once WebComponents become streamlined none of these will matter.
And now they still matter lol
02:08 setup() method
React hooks?
Sorry but starting the video saying that Vue comps become unreadable and less maintainable when they get bigger as a confirmation so React and Angular comps are real mess in the same situation otherwise beginners will think only Vue have this issue and I do not agree on the Typescript limitations point. And btw all of them are fine to me, it's all about how far you go with your atomic architecture design and where to set the comp logic either locally or globally depending on the feature.
Good demo though ;)
It is a kind of constructor in angular =))
You should change the "Ding" sound
AMAZING!!
Whatever you do, don't fall into the angularJs paradigm. They made it better, but.. well we know
Didn't Vue class component already fix a lot of the Vue 2 issues?
Composition API is like services in Angular.
No entiendo para que sacaron Vue 4.x.x???, tiene full errores.
VUEJS = best javascript framework
you used classic binding wo shorthands for noobs? )) great stuff anyway
I think VueMastery has got a good concept but the explanations are suited for people who have years of experience using vue or react. They fail miserably with true beginners. Videos tutorials should enhance the comprehensibility of the documentation; in this case, for instance, understanding Vuex is a lot simpler in the docs, than watching the whole course about Vuex on vueMastery.
Whats wrong with using OOP in your app instead of trying to reinvent the wheel? Just make an order and sorting object or an ResultSet Object which has these methods. This problem vue tries to fix can be easy fixed with OOP.
similar to Svelte use
I loVue
composition api make vue development more like es is
Is it just me or you look like Malcom Gladwell
Why would you even think so ?? Maybe I've had a habit of seeing Gladwell's hair, he doesn't resemble MG in any way.
Having a problem of logic and presentation separation in 2019 is beyond absurd.
How did you come up with the name Vue?
I like the green shirt
TS itself is a drawback 😬
Exactly why Angular failed. Now I can start learning react. Go to hell vue
they aren't making it anymore complicated to make an app with vue they are just adding another way for the people that want to use it. This new api is very useful for bigger apps. But when you're learning you don't have to use this new api. As a person who like typescript I am also happy they are making this change since there will be better typescript support with it.So this isn't exactly why angular failed. Angular failed because they completely rewrote the entire framework changing the syntax and everything without any warning and no backwards compatibility.
Vue 3 looks bloated and complicated. This is "simplifying" with added complexity. So begins the trip of an ugly monolith.
The composition API is just for people who don't understand Single Responsibility and who can't keep out logic from a component.
"There is another way... another syntax... ". Dude just use React + JSX + Mobx + TypeScript... :D
JSX sucks
@@johanw2267 Highly professional answer. Any arguments for this opinion?
@@Thomas-jj1ev It has been written about 100 times. One google search away. tldr; readability, mixing too much html with JS, className etc.
@@johanw2267 seriously the worst answer you can give, you sound like just another youtuber chilling his opinion without even working day by day with it in a very big project. :D
@@Thomas-jj1ev Not really. I'm not here to educate you. Do your own research.
Behold! Vue will not be simple anymore. The team started to get bored and add more shits to it. This's sad :(
I don't how this is not simple. Looks to me way more logical
Use sveltjs
Please destroy ReactJS already
You must be very smart to see a difference in the same shit.
So you destroy react by copying everything what react does. Hmm ok
Then why is Vue using hooks?
if you want to reuse code and have a clean project structure, then use Angular , not Vue :D ... just funny this composition api, nothing special .. same mess in Vue... i would never use vue for my personal projects
MESSINS :) You did it all wrong at the first place and now is fixing it in another wrong way. Your framework is conceptually wrong that's why you struggle with everything.