I’m happy with React, typescript support is better and I hate the one large file. I hate the overuse of double quotes with everything. It feels wrong having JavaScript code in double quotes.
Why would anyone be tired of React? It's ok, especially if you use hooks and you're familiar with its great ecosystem. Tried Vue and I won't say that it's better than React.
React is like early versions of php, just 1 big hack. Vue is so elegant, everything is neat and you go a long way with just standard js and html knowledgea
I love Vue so much but have switched to React for three reasons: 1. Composing components with hooks leads to generally much cleaner and reusable components, which are also easier to maintain. 2. Bigger ecosystem 3. Much easier to find developers to add to your team(which was the main reason I switched in the first place) I must admit though that Nuxt is the absolute best framework Ive used. I mostly use Next.js now but it is not as great as nuxt, not by a long shot
@@AngelHdzMultimedia yeah I know and the composition api is really awesome. The only problem though is that single file components dont allow for multiple components in the same file (hence the name) which can be a hassle when organizing your code. Yes I could use jsx and vue render functions but that sort of removed a lot of the benefits with using vue. So the composition api is very similar to hooks in certain ways but falls short in others.
I started learning web dev with vue, I became bored and felt like I wasn't learning JS enough so I quit. Then I discovered React and it forced me to use JS more and to really understand how everything fits together. Gatsby, Next and TS make development fun as hell and there's so many cool paths you can take. Just my experience as a noob.
Haha! I love these videos. Both are really fantastic frameworks. The layout and setup of codebase is very different. It comes down to personal comfort and preference as to which pattern developers enjoy. React and Vue patterns will appeal to developers of all types depending on their learning curve and how easy the pattern becomes habit during the learning phase. Of the two. I prefer React but I do consider that Vue has less restrictions and barrier to development. React is very freaking picky about the code base. Which can be frustrating.
I personally really like having map() in my JSX. It's mostly "just" JavaScript. By the way, you can have "slots" because you can accept React components as props in your component. For events, you could take a look at useReducer. It returns a dispatch function which your reducer can listen for. You could also put the dispatch from useReducer or simply setState from useState into a React Context if you need it deep inside a component tree.
I think this is another failure of Vue, slots and the scope binding to slots (can't remember what its called exactly) - this is (bad) DSL that you have to actively learn & it easily gets confusing unless you use it daily. Feels very unnatural. Whereas with React it is just another property :-)
Huh. Have to say, I never properly used useReducer, but it's indeed a very good alternative to the event system in Vue, more modular etc. React context is amazing too.
Just a side note. Don’t code under /mnt if youre using wsl as it’s slow as hell. Instead, use native filesystem and put your project under /home/youruser
I prefer Vue, but generally don't mind React too. However, I'm intrigued to hear that you prefer slots and emitting events in Vue over children props and passing functions down from React. I prefer the way React does those tbh. Either way I think it just proves the point that instead of arguing over which is better than the other, instead just learn to appreciate that there is a lot of middle ground shared between the two and embrace them both as devs.
You should try it with styled-components, its a magical world that lets you bring js directly into your css which opens a world of possibilities - I'm a Vue developer now bc of work, but previously React and that also my preference to work with. Vue has a sort of halfway implementation of styled-components available, but its nowhere near the same and also breaks vue-jest. To get single-file components with styled-components like in Vue just put "export styled(YourComponent)`your styles`; at the end of your component file after importing styled from styled-components. You also have to then destruct className from the component props and apply this to the outermost element in the component as className. Not only will this allow you to style your component, but it will allow you to use props, set custom attributes, overriding the style on other child components by referencing the actual component name, and much more. Trust me when I say Vue has nothing like it, and its what I miss most about React. Thats not even to get started on theming in styled-components which is absolutely brilliant...
I like that React doesn't tell you what libraries you should use, it is great to have a lot of options and a lot of new and great libraries come out! In the end a lot of the big companies that use react might end up creating their own custom solutions. edit: you could use css in js to get the css on the same file, this even sometimes improve css size on big projects! :)
Vue doesn't tell you what libraries to use either. The CLI gives you options where it will automatically set things up for you, but even then you'll chose which one you want. You can chose a preset or manually pick each setting, and when you're done manually picking things, it gives you the option to save that as a preset. For manual selections, the core options pertain to the version of Vue (2.X or 3.x), whether or not to set up Babel and/or Typescript, whether or not to set up PWA scaffolding, the Vue Router, Vuex, and which css preprocessor/linter/formatter/unit testing/end to end testing to set up (if any, with all sorts of combinations possible). There are third party plugins for the Vue CLI to add GraphQL/Apollo, component libraries, Electron support, i18n, Storybook, etc. 57 pages of results if you search npmjs.com for vue-cli-plugin. Seriously, I've seen people that preferred Redux to Vuex and so they used Redux instead, though admittedly, I don't think anyone has set up a Redux plugin for Vue CLI yet. If the Vue CLI doesn't have a plugin for something you want, you can just not specify anything for the relevant feature and then configure it manually. That's all the Vue CLI really is, a shortcut to avoid having to manually configure everything. It's even designed such that you can add a new plugin and update your project without having to start over. I think this is important for Vue because a lot of people are picking up Vue as their first framework/library, so they're not familiar with how to set up babel, typescript, jest, and all the other things that they may want to use. It lowers the barrier to entry. For people that already know how to set that up, they can skip Vue CLI completely. Even as a total newbie to Vue, I skipped the Vue CLI once in a while. This is quite a bit better than some other frameworks/libraries I've played around with, including earlier versions of Vue, where initializing a new project basically consists of copying a template that just happens to include the features that you want, and if you want a mix of features that don't have a corresponding template, you have to tweak it by hand. I'm not saying that Vue is all sunshine and roses and is the best frontend framework/library/whatever. I don't think there's any such thing as every framework and library makes different tradeoffs. I'm just pointing out that this particular bit of criticism, if I understand it correctly, isn't as accurate as it might seem.
@@erics2133 I was mainly referring to the official routing and state solutions, it has its pros and cons but this is a big difference between React and Vue and how they develop their own frameworks.
@@devtor7451 Right, except that neither of those are part of Vue and they're not forced on you. Vue is a view layer and reactivity system, and beyond that, it's unopinionated. The Vue community is more opinionated, but if you want to use a different router or store (there are alternatives, even Vue specific alternatives), you can.
@@erics2133 The vue team works on vuex and vue router, that is what I am referring to, they are not forced but they are encouraged, yes you can use anything you want but it doesn't change the fact that it is the official solution. Vue builds an ecosystem while React doesn't and that is the major difference I am referring to.
I’d argue having a framework be a bit opinionated is better than a completely non opinionated framework. Especially since the tools you’ll be using are first party packages supported by the framework team. E.g. VueX & VueRouter. Also I like React, but Vue’s scoped styling is far superior to css in js
I still think Vue is King, especially due to separating HTML and JavaScript. (1) Also enforcing props makes it that it's easier for teams to understand what a child component requires. (2) I like the passing functions in React, but emitting events and Slots in Vue which is like @Output and @Input in Angular is an essential of a JS framework to enable a child component to communicate to a parent Component. (3)
I'm a React dev and I have to say that Vue beats React in styling 100%, when you compare them out of the box. Vanilla React begs for a styled-jsx or styled-components library. Also use of JSX, and the problem you had with the click handle are not done as well in React. In the end they're very similar and neither is significantly better than the other... let's leave Angular out of the comparison for obvious reasons ;)
If you use create-react-app, styling with css (CSS Module too) was supported by default. If you want to use sass, only thing you need to do is install node-sass as dependency. CSS in js is just a popular option in many option for styling for React project.
React can be added progressivly but need some initial effort to make jsx buildtime transpiled then you mixin React anywhere you want. I did this on my company but, ye you right there is no good way to use jsx only by adding script tag.
I think Vue is way more sorted than this. The click handler on the button was weird. This className thing - why i can't be a normal HTML attribute? I've seen nothing in this vid that i would say is better than in Vue.
It can’t really be a “normal” html attribute because JSX is only an abstraction over a function call. The native representation of the class attribute in the DOM is in fact className, which is the same thing you’d use with vanilla JS.
MobX would give you computed properties and a more "vue-like" react. Also, you should have set an empty array as a dependency of the "useEffect" hook, otherwise the hook will be triggered every time props or state changes.
I like Vue more but react nice as well. I like react passing functions vs Vue emitting events. Plus Vue tooling needs some improvement. And typescript support. Otherwise Vue wins in other areas for me
this is cool! but you should get a React developer to join you to help you, as they could clarify a few things on the fly :) (i felt the same with Ben's video :p)
Hi, thanks for all the vue videos, I learned tons and I also have purchased one of your courses. I am interested to use algolia search with a firestore project I have, could you make a video on that?
I used JSX in Vue before so this is really familiar to me, as much as I love the simplicity of Vue template, I actually find JSX making more sense as it's just javascript after all .. for example I know that in events you can call a prop function without using arrow function if you don't need to pass any parameters by just passing the function name without parentheses .. just normal javascript.
I learned and used Vue first, then studied React later (for hobby purpose), but then after 1 day of trying, I refused to continue because it is too ugly
I'm sorry but until further notice: 1. Vue 2. Svelte 3. Vanilla js 3. Angular (maybe) 4. React (really?) 4 and 5 are in no particular order. I can never have appetite for React, I won't even try anymore. Thanks for the insights Erik.
@@glitchedbyte747 the learning curve of Angular is too high and also the docs is lil bit hard to understand and also overhead API. Vue is also overhead API imo
I would love some similar comparison regarding Vuex and React Redux. The first one took me some time to get but now it makes complete sense to me... but Redux really messes my head. I know the principle is the same but Vue's terminology feels much easier.
Vue 3 improved it's typescript support but react support is still better. Also redux vs vuex ts support is not even the competition. And redux can be used without react. But there are some things that are better in vue. Vue router is much cleaner than react router. And have a lot of stuff like auth guards out of the box. There is not alternative to v-model in react (you have to implement it by your self)
Here is my ranking (IMO) 1. React.js - it will show you who you are (your own style, how you compose/code/organize/optimize/etc) 2. Svelte - Vue-ish but more performant (developer friendly). P.S. Sorry Vue.js 3. Vue.js - React-ish and Angular-ish (developer friendly). P.S. sorry Angular.js 10. Angular.js - everything you need is there and also everything you don't need (developer friendly but a fake friend)
I'm surprised you prefer the Vue style of predefining your props. This was one of the big headaches for me when i used Vue because you can't do stuff like `const { a, b, c, ..rest } = props` which is kind of essential in some react libraries (Redux Form/Formik, and more) and which would have been super nice with Vue as well (actually made an issue & discussed this problem with one of the core members a long time ago) Also, props in Vue are checked at runtime (!) whereas with React + Typescript (which is the standard when working with React today) you would define a typescript interface which would be checked at compile time. Vue 3 has better typescript support, but you still have to work with hacks to get decent type-checking of your props. I liked Vue 2, i think Vue 3 is just a desperate attempt at copying react, it doesn't feel like a natural API at all to me. I wish Vue 2 came without a template engine (just JSX) - if it did i would've switched then and there because Vue's reactivity system, computed properties, efficient diffing is just way better & easier to work with than what you've got with react.
To elaborate on the "without template engine" part; i just want clear stack traces, not some internal stack traces of observables or the template engine, when i do something wrong. JSX is simple in the sense that it's transpiled in-place to JS, so its easy to follow.
I feel once you start using Redux the react app will get complex and hectic.. Vuex is breezeway.. I found vue scoped css is great which is needs work around in React.. But both are greate frameworks.. Also I worked with Angular the folder structure and modules makes it complex but it's also a good framework. . BTW scoped css is concept from Angular brought into vue 😅
I've used vue for 2 years+ but I switched to react eventually. And most companies I've seen requires deep knowledge in js + react . It sounds like my 2years+ in vue have just thrown away, Till now since the day I've moved to react I've never touched vue. Just watching Evan's vue update
My god more and more videos about this Vue vs React debacle. I'll give you a really simple point of view about that: Programmers prefer React. Designers prefer Vue. By programmers I mean people really comfortable writing code, usually the more experienced across the board. As an example, people coming from backend development with a cs degree will choose 60% of times React. That's because React is more easy to grasp in the function (params) => UI paradigm. On the contrary, there are people less comfortable writing really complex pieces of code therefore they want everything wired up and ready to be served. Those kind of people usually come from the creative fields. As an example a UI/UX designer will be more inclined towards Vue. Also, I think React is still king for a simple reason: in a real company environment the thing making the most important difference is not the learning curve, is the scalability of the project. Therefore, learning React is more complicated (that's not true for software developers) but will be easier to scale up when many people are working on the same project. Moreover the maturity of the project makes a ton of difference. React is more mature and is backed up by facebook, the documentation is useless once you get it and there's more professional support when you want to use some UI library. React took many years to get there, Vue will definitely do the same trip, but now it's not up for the task Right now
All of that jsx + typescript has nothing common with vanilla. It’s just an unreadable mess with 1mln imports everywhere. Simple things should be simple and that’s about nuxt, where everything is clear and structured and you don’t need to config your config how to config.
I find the react vs. vue discussion boring. Most comparisons concentrate on the outside, very few actually take a look under the hood what the real differences beside syntax, github stars or community acceptance are. Who cares? It's undeniable that with both frameworks you will get the job done. I welcome that there is a competition which means choice and constant improvement.
@@siya.abc123 These are the best things that have happened to react, these features are gonna improve readability of the code and make code more understandable
as a React and Vue developer I totally agree. Typescript is just lil bit pretty well in vue-class-component and add vue-property-decorator makes a lil bit easier to handle a lot of overhead API from Vue.
@@internet4543 you are saying that you are better? I could bet that only thing you know is install packages. But that's ok. You are such a good dev. Lol
It’s actually very nice once you get used to it imo. You don’t need to use JSX in React but it’s even more painful than manipulating DOM elements in vanilla JavaScript.
@@fxmtoeclipse Maybe but markup and code should be kept separate. Embedding one in the other violates the entire idea of it. I shouldnt have to change code to change the look of something that uses HTML. To this point React just forgets basic design principles.
separation of code does NOT equal separation of concerns. React did not break design patterns, they embraced it with encapsulation and modularity through the functional paradigm to make high performant apps.
Interested in learning Vue? Tired of React? Sign up here! :) bit.ly/2vFWBQi
I’m happy with React, typescript support is better and I hate the one large file. I hate the overuse of double quotes with everything. It feels wrong having JavaScript code in double quotes.
Why would anyone be tired of React? It's ok, especially if you use hooks and you're familiar with its great ecosystem. Tried Vue and I won't say that it's better than React.
React is like early versions of php, just 1 big hack. Vue is so elegant, everything is neat and you go a long way with just standard js and html knowledgea
@@martinlukasik431 Vue is getting hooks and other goodies in version 3, and it still remain being minimalist and easy to work with.
Interested in learning Vue? Yes
Tired of React? Not at all
Welcome to the dark side, let's see some tsx next 😜
REACT is the king
Just putting it out there. Ben and Erik, ya'll are my favs 😊
@@Alekobeats I was just about to comment the same thing, let's see a collab
©️⭕LL🅰️🅱️
I clicked on this video just for reading Ben's comment.
Let's Vue this video and React to it :)
this make sense 😃
I love Vue so much but have switched to React for three reasons:
1. Composing components with hooks leads to generally much cleaner and reusable components, which are also easier to maintain.
2. Bigger ecosystem
3. Much easier to find developers to add to your team(which was the main reason I switched in the first place)
I must admit though that Nuxt is the absolute best framework Ive used. I mostly use Next.js now but it is not as great as nuxt, not by a long shot
Oh and 4. Awesome typescript support, and once you switch it is very hard to go back to vanilla js
Vue 3 is getting hooks.
@@pigeonnnn Are you looking to add more developers to your team? Asking for a friend. 😀
@@AngelHdzMultimedia yeah I know and the composition api is really awesome. The only problem though is that single file components dont allow for multiple components in the same file (hence the name) which can be a hassle when organizing your code. Yes I could use jsx and vue render functions but that sort of removed a lot of the benefits with using vue. So the composition api is very similar to hooks in certain ways but falls short in others.
@@sogggy hahaha not right now unfortunately ☹️
I started learning web dev with vue, I became bored and felt like I wasn't learning JS enough so I quit. Then I discovered React and it forced me to use JS more and to really understand how everything fits together.
Gatsby, Next and TS make development fun as hell and there's so many cool paths you can take.
Just my experience as a noob.
Exactly. React. No magic, just pure JS.
I am a vue advocate myself (just look at my channel), but react beats vue in typescript support hands down.
Haha! I love these videos. Both are really fantastic frameworks. The layout and setup of codebase is very different. It comes down to personal comfort and preference as to which pattern developers enjoy.
React and Vue patterns will appeal to developers of all types depending on their learning curve and how easy the pattern becomes habit during the learning phase.
Of the two. I prefer React but I do consider that Vue has less restrictions and barrier to development. React is very freaking picky about the code base. Which can be frustrating.
Thanks for your feedback!
I learned Vue first and then learned React. I really, really missed how clean Vue was compared to React.
So why did you switch?
@@AndrewRusinas more jobs require react
I personally really like having map() in my JSX. It's mostly "just" JavaScript.
By the way, you can have "slots" because you can accept React components as props in your component.
For events, you could take a look at useReducer. It returns a dispatch function which your reducer can listen for.
You could also put the dispatch from useReducer or simply setState from useState into a React Context if you need it deep inside a component tree.
I think this is another failure of Vue, slots and the scope binding to slots (can't remember what its called exactly) - this is (bad) DSL that you have to actively learn & it easily gets confusing unless you use it daily. Feels very unnatural. Whereas with React it is just another property :-)
Thanks for the tips! I'll check out useReducer
Huh. Have to say, I never properly used useReducer, but it's indeed a very good alternative to the event system in Vue, more modular etc.
React context is amazing too.
Just a side note. Don’t code under /mnt if youre using wsl as it’s slow as hell. Instead, use native filesystem and put your project under /home/youruser
Good to know! I’ll try that next time
Yo Ben, can you come review this please
create-react-app have --template option. So you can create your own template with pre-install packages/configs to reuse over and over
I prefer Vue, but generally don't mind React too. However, I'm intrigued to hear that you prefer slots and emitting events in Vue over children props and passing functions down from React. I prefer the way React does those tbh. Either way I think it just proves the point that instead of arguing over which is better than the other, instead just learn to appreciate that there is a lot of middle ground shared between the two and embrace them both as devs.
True! I think if I had to work in React everyday, i'd get use to passing functions down
In React, you'll appreciate JavaScript more.
You should try it with styled-components, its a magical world that lets you bring js directly into your css which opens a world of possibilities - I'm a Vue developer now bc of work, but previously React and that also my preference to work with. Vue has a sort of halfway implementation of styled-components available, but its nowhere near the same and also breaks vue-jest. To get single-file components with styled-components like in Vue just put "export styled(YourComponent)`your styles`; at the end of your component file after importing styled from styled-components. You also have to then destruct className from the component props and apply this to the outermost element in the component as className.
Not only will this allow you to style your component, but it will allow you to use props, set custom attributes, overriding the style on other child components by referencing the actual component name, and much more. Trust me when I say Vue has nothing like it, and its what I miss most about React. Thats not even to get started on theming in styled-components which is absolutely brilliant...
Be great if you would create a vue ecommerce tutorial like Brad Traversy's React ecommerce tut. Thank you for all your great content!
I'm a React developer who has been learning a lot of Vue in the last week. Cool to see the flip side.
Vue Developer here looking to learn React! Impeccable timing! Also what keyboard are you using? It sounds so nice.
Thanks, now i like vue even more :)
@@internet4543 what a broken analogy xD
For me, I literally throw a piece of change to chose between vue and react and I'm happy with the result 👌
I like that React doesn't tell you what libraries you should use, it is great to have a lot of options and a lot of new and great libraries come out! In the end a lot of the big companies that use react might end up creating their own custom solutions.
edit: you could use css in js to get the css on the same file, this even sometimes improve css size on big projects! :)
Vue doesn't tell you what libraries to use either. The CLI gives you options where it will automatically set things up for you, but even then you'll chose which one you want. You can chose a preset or manually pick each setting, and when you're done manually picking things, it gives you the option to save that as a preset.
For manual selections, the core options pertain to the version of Vue (2.X or 3.x), whether or not to set up Babel and/or Typescript, whether or not to set up PWA scaffolding, the Vue Router, Vuex, and which css preprocessor/linter/formatter/unit testing/end to end testing to set up (if any, with all sorts of combinations possible).
There are third party plugins for the Vue CLI to add GraphQL/Apollo, component libraries, Electron support, i18n, Storybook, etc. 57 pages of results if you search npmjs.com for vue-cli-plugin.
Seriously, I've seen people that preferred Redux to Vuex and so they used Redux instead, though admittedly, I don't think anyone has set up a Redux plugin for Vue CLI yet. If the Vue CLI doesn't have a plugin for something you want, you can just not specify anything for the relevant feature and then configure it manually. That's all the Vue CLI really is, a shortcut to avoid having to manually configure everything. It's even designed such that you can add a new plugin and update your project without having to start over.
I think this is important for Vue because a lot of people are picking up Vue as their first framework/library, so they're not familiar with how to set up babel, typescript, jest, and all the other things that they may want to use. It lowers the barrier to entry. For people that already know how to set that up, they can skip Vue CLI completely. Even as a total newbie to Vue, I skipped the Vue CLI once in a while.
This is quite a bit better than some other frameworks/libraries I've played around with, including earlier versions of Vue, where initializing a new project basically consists of copying a template that just happens to include the features that you want, and if you want a mix of features that don't have a corresponding template, you have to tweak it by hand.
I'm not saying that Vue is all sunshine and roses and is the best frontend framework/library/whatever. I don't think there's any such thing as every framework and library makes different tradeoffs. I'm just pointing out that this particular bit of criticism, if I understand it correctly, isn't as accurate as it might seem.
@@erics2133 I was mainly referring to the official routing and state solutions, it has its pros and cons but this is a big difference between React and Vue and how they develop their own frameworks.
@@devtor7451 Right, except that neither of those are part of Vue and they're not forced on you. Vue is a view layer and reactivity system, and beyond that, it's unopinionated. The Vue community is more opinionated, but if you want to use a different router or store (there are alternatives, even Vue specific alternatives), you can.
@@erics2133 The vue team works on vuex and vue router, that is what I am referring to, they are not forced but they are encouraged, yes you can use anything you want but it doesn't change the fact that it is the official solution. Vue builds an ecosystem while React doesn't and that is the major difference I am referring to.
I’d argue having a framework be a bit opinionated is better than a completely non opinionated framework. Especially since the tools you’ll be using are first party packages supported by the framework team. E.g. VueX & VueRouter. Also I like React, but Vue’s scoped styling is far superior to css in js
Thank you for the video, Erik. And a question: what is the name of the theme you are using :)?
That was pretty cool and helpful! Thanks Erik!
I still think Vue is King, especially due to separating HTML and JavaScript. (1)
Also enforcing props makes it that it's easier for teams to understand what a child component requires. (2)
I like the passing functions in React, but emitting events and Slots in Vue which is like @Output and @Input in Angular is an essential of a JS framework to enable a child component to communicate to a parent Component. (3)
@@molesarecoming Thank you for taking your time to respond, I will for sure read that article. Thanks
I'm a React dev and I have to say that Vue beats React in styling 100%, when you compare them out of the box. Vanilla React begs for a styled-jsx or styled-components library.
Also use of JSX, and the problem you had with the click handle are not done as well in React.
In the end they're very similar and neither is significantly better than the other... let's leave Angular out of the comparison for obvious reasons ;)
I do like scoped css built in in Vue, in the same file.
If you use create-react-app, styling with css (CSS Module too) was supported by default. If you want to use sass, only thing you need to do is install node-sass as dependency. CSS in js is just a popular option in many option for styling for React project.
React can be added progressivly but need some initial effort to make jsx buildtime transpiled then you mixin React anywhere you want. I did this on my company but, ye you right there is no good way to use jsx only by adding script tag.
I think Vue is way more sorted than this. The click handler on the button was weird. This className thing - why i can't be a normal HTML attribute? I've seen nothing in this vid that i would say is better than in Vue.
It can’t really be a “normal” html attribute because JSX is only an abstraction over a function call. The native representation of the class attribute in the DOM is in fact className, which is the same thing you’d use with vanilla JS.
@@fxmtoeclipse thx for the explanation
loved VUE even more
It would be interesting to compare to the Vue Render API where you also use JSX
MobX would give you computed properties and a more "vue-like" react. Also, you should have set an empty array as a dependency of the "useEffect" hook, otherwise the hook will be triggered every time props or state changes.
It seems like Erik is clashing Ben Awad.
I like Vue more but react nice as well. I like react passing functions vs Vue emitting events.
Plus Vue tooling needs some improvement. And typescript support.
Otherwise Vue wins in other areas for me
Es6/7 snippets extension is what you were looking for.
This is madness x), by the way I'd still prefer vue js
haha
this is cool! but you should get a React developer to join you to help you, as they could clarify a few things on the fly :) (i felt the same with Ben's video :p)
Hi, thanks for all the vue videos, I learned tons and I also have purchased one of your courses. I am interested to use algolia search with a firestore project I have, could you make a video on that?
i use the ' es7 React/Redux/GraphQl/React Native ' snippet
Ever since I've switched to TypeScript with React I see no purpose for prop-types.
I used JSX in Vue before so this is really familiar to me, as much as I love the simplicity of Vue template, I actually find JSX making more sense as it's just javascript after all .. for example I know that in events you can call a prop function without using arrow function if you don't need to pass any parameters by just passing the function name without parentheses .. just normal javascript.
I learned and used Vue first, then studied React later (for hobby purpose), but then after 1 day of trying, I refused to continue because it is too ugly
I am trying man I am trying love react
I'm sorry but until further notice:
1. Vue
2. Svelte
3. Vanilla js
3. Angular (maybe)
4. React (really?)
4 and 5 are in no particular order.
I can never have appetite for React, I won't even try anymore.
Thanks for the insights Erik.
Naw, Angular is still worse. It's closer after seeing this, but Angular will always be bottom.
@@sp00k1es Why is Angular still worse? :o
@@glitchedbyte747 Just my personal experience that it's the most unintuitive and hard to manage.
@@glitchedbyte747 the learning curve of Angular is too high and also the docs is lil bit hard to understand and also overhead API. Vue is also overhead API imo
hi, please create a video about jobs queue with nodejs or express..
Which vscode theme are you using in this video?
I would love some similar comparison regarding Vuex and React Redux. The first one took me some time to get but now it makes complete sense to me... but Redux really messes my head. I know the principle is the same but Vue's terminology feels much easier.
I think comparing VueX to Redux is a bit unfair. I’d argue MobX is a better comparison
I like both, but I like more Vue!
npx create-react-app has got me struck to begin using react 😬
Vue 3 improved it's typescript support but react support is still better.
Also redux vs vuex ts support is not even the competition. And redux can be used without react.
But there are some things that are better in vue.
Vue router is much cleaner than react router. And have a lot of stuff like auth guards out of the box.
There is not alternative to v-model in react (you have to implement it by your self)
You could just use TypeScript with react for types
Hey erik, why didnt you say at the end, "Vue is still King"?
That's because React is King ;)
Ha! I did say that!
lol
LOL
@@bawad Redux suckkkkssss and makes React complex. .. vuex is legend
And now we have two kings and no queen
thank U
What's your color theme? Thanks, stay safe!
Synthwave 84!
@@ProgramWithErik thanks sir!
Here is my ranking (IMO)
1. React.js - it will show you who you are (your own style, how you compose/code/organize/optimize/etc)
2. Svelte - Vue-ish but more performant (developer friendly). P.S. Sorry Vue.js
3. Vue.js - React-ish and Angular-ish (developer friendly). P.S. sorry Angular.js
10. Angular.js - everything you need is there and also everything you don't need (developer friendly but a fake friend)
Thank God its your Rankings 😂😂
I'm surprised you prefer the Vue style of predefining your props. This was one of the big headaches for me when i used Vue because you can't do stuff like `const { a, b, c, ..rest } = props` which is kind of essential in some react libraries (Redux Form/Formik, and more) and which would have been super nice with Vue as well (actually made an issue & discussed this problem with one of the core members a long time ago)
Also, props in Vue are checked at runtime (!) whereas with React + Typescript (which is the standard when working with React today) you would define a typescript interface which would be checked at compile time. Vue 3 has better typescript support, but you still have to work with hacks to get decent type-checking of your props.
I liked Vue 2, i think Vue 3 is just a desperate attempt at copying react, it doesn't feel like a natural API at all to me. I wish Vue 2 came without a template engine (just JSX) - if it did i would've switched then and there because Vue's reactivity system, computed properties, efficient diffing is just way better & easier to work with than what you've got with react.
To elaborate on the "without template engine" part; i just want clear stack traces, not some internal stack traces of observables or the template engine, when i do something wrong. JSX is simple in the sense that it's transpiled in-place to JS, so its easy to follow.
try nextjs, it's like create-react-app but better
I feel once you start using Redux the react app will get complex and hectic.. Vuex is breezeway.. I found vue scoped css is great which is needs work around in React.. But both are greate frameworks.. Also I worked with Angular the folder structure and modules makes it complex but it's also a good framework. . BTW scoped css is concept from Angular brought into vue 😅
@@internet4543 yup if the app grows we need some state manager.. Recoil is awesome.. Doing the same job with ease
That's great!
I've used vue for 2 years+ but I switched to react eventually.
And most companies I've seen requires deep knowledge in js + react .
It sounds like my 2years+ in vue have just thrown away, Till now since the day I've moved to react I've never touched vue. Just watching Evan's vue update
I see lots of job postings in my area where they require "React, Vue and Angular" in that particular order. I'd prefer Vue over Angular any day.
@@DavidSmith-ef4eh Most large companies are maintaing react/ angular with djanggo backend 😆
@@kolya7921 Yeah, probably angularJS, not angular lol.
@@DavidSmith-ef4eh angular
Ben Awad is watching
how you know?
@@jancifoxhound6380 React Vs Vue the reason
Is this a Ben's response?
My god more and more videos about this Vue vs React debacle. I'll give you a really simple point of view about that:
Programmers prefer React.
Designers prefer Vue.
By programmers I mean people really comfortable writing code, usually the more experienced across the board. As an example, people coming from backend development with a cs degree will choose 60% of times React. That's because React is more easy to grasp in the function (params) => UI paradigm.
On the contrary, there are people less comfortable writing really complex pieces of code therefore they want everything wired up and ready to be served. Those kind of people usually come from the creative fields. As an example a UI/UX designer will be more inclined towards Vue.
Also, I think React is still king for a simple reason: in a real company environment the thing making the most important difference is not the learning curve, is the scalability of the project. Therefore, learning React is more complicated (that's not true for software developers) but will be easier to scale up when many people are working on the same project. Moreover the maturity of the project makes a ton of difference. React is more mature and is backed up by facebook, the documentation is useless once you get it and there's more professional support when you want to use some UI library.
React took many years to get there, Vue will definitely do the same trip, but now it's not up for the task Right now
Where'd you get those percentages lol.
Facebook does not open source the version they use in production
Very interesting. Next time Angular maybe? :D
Yeah, I should do that
Now Vue3 is really a lot better than it was, and React for me seems like a hassle, and an unnecessary one :( Too bad that it has much more job offers.
You always say in the beginning of your post “react angular and vue lover”. Why you try react only now? Hmm.
All of that jsx + typescript has nothing common with vanilla. It’s just an unreadable mess with 1mln imports everywhere. Simple things should be simple and that’s about nuxt, where everything is clear and structured and you don’t need to config your config how to config.
I find the react vs. vue discussion boring. Most comparisons concentrate on the outside, very few actually take a look under the hood what the real differences beside syntax, github stars or community acceptance are.
Who cares? It's undeniable that with both frameworks you will get the job done. I welcome that there is a competition which means choice and constant improvement.
Hello from Ban Awad :)
Banworld
Kind felt like bashing react while gasLighting vue for 30 minutes straight.
UseReducer, useContext, useMemo.
We need a part two of you going over these parts.
I don't know what that is but it sounds messy already
That would be interesting...
@@siya.abc123 it was messy for the first two weeks I tried it, now it seems pretty natural while writing react code
@@siya.abc123 These are the best things that have happened to react, these features are gonna improve readability of the code and make code more understandable
Vue with typescript is horrific
I don't know React, but I agree Vue with Typescript is not really pretty.
Once they get all these upstream bugs in V3 for vue-router, and all the plugins, I think it will approach being pleasant.
@@sp00k1es I've been using vue-router@next and it's pretty good!
@@CodingUnited It's been a while since I tried, that's good to know it's gotten the attention it needed.
as a React and Vue developer I totally agree. Typescript is just lil bit pretty well in vue-class-component and add vue-property-decorator makes a lil bit easier to handle a lot of overhead API from Vue.
Try BTC
Thanks Ben... ERM.........I mean Erik
lol are you copying all from your other screen xD
Of course, you need to be prepared when there is a presentation. xD
I think you explain too much unnecessary things than coding. I would liked to see more you would do in the React from coming from Vue
Never use JavaScript, anyone watching this please ensure you use typescript. Declare your props in an interface.
Or use PropTypes
@@migueldomingos4570 you could use prop types but they are not that good imo. definitely prefer declaring types/interfaces more.
@@jmon24ify I agree bro. I also.prefer typescript. But some people only know js
no
@@justintie Very informative
Im i the only on that doesn't like the way react code looks?
You are not alone, i will always stick with Vue just because of this, is ultra-important for me.
@@internet4543 you are saying that you are better? I could bet that only thing you know is install packages. But that's ok. You are such a good dev. Lol
Once you go react you never go back.
Cope
React is terrible. Embedding html inside javascript?!? That breaks every common sense design pattern ever invented.
Well that's what its designed for, to embed JS in HTML or embed HTML in JS.
It’s actually very nice once you get used to it imo. You don’t need to use JSX in React but it’s even more painful than manipulating DOM elements in vanilla JavaScript.
@@fxmtoeclipse Maybe but markup and code should be kept separate. Embedding one in the other violates the entire idea of it. I shouldnt have to change code to change the look of something that uses HTML. To this point React just forgets basic design principles.
Actually its not just hmtl inside javascript, its html inside javascript which then is put inside html and switched dynamically.;p
separation of code does NOT equal separation of concerns. React did not break design patterns, they embraced it with encapsulation and modularity through the functional paradigm to make high performant apps.
Angular is still King.
I like how you are cheating from other monitor :))))
react > vue
React wins
Dislike for trying React Crap :(
That's one ugly code lol. It's like forcing yourself to eat something that you dont like. Welcome back to the 90s boys