🔥 If you're learning to code, check out my website 👉 codehawke.com/all_access.html 🔥 Learn more 👉 ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-fpp215OSRV0.html
Chris 2018 -> is Vue better than React? Chris 2019 -> Why we should ditch React : )) Since you're using vue, i recommend checking out Tailwind with Vue + CSS Modules(optional) ... the workflow just makes so much sense for a dev who uses Vue... i think tailwind approach to css + CSS Modules is the future ... I actually discovered Tailwind via State of CSS 2019 polls , and the developers Satisfaction and Interest rate of using it was so high, that i had to check it out and wasn't dissapointed. I thought Bulma is so good, but Tailwind is even better. Most CSS frameworks do too much. They come with all sorts of predesigned components like buttons, cards, and alerts that might help you move quickly at first, but cause more pain than they cure when it comes time to make your site stand out with a custom design. Tailwind is different. Instead of opinionated predesigned components, Tailwind provides low-level utility classes that let you build completely custom designs without ever leaving your HTML. Tailwind provides tools for extracting component classes from repeated utility patterns, making it easy to update multiple instances of a component from one place: Button Button Button .btn { @apply font-bold py-2 px-4 rounded; } .btn-blue { @apply bg-blue-500 text-white; } .btn-blue:hover { @apply bg-blue-600; } Tailwind is written in PostCSS and configured in JavaScript, which means you have the full power of a real programming language at your fingertips. Tailwind is more than a CSS framework, it's an engine for creating design systems. // tailwind.config.js module.exports = { theme: { screens: { tablet: '768px', desktop: '1024px', }, colors: { primary: { 100: '#ebf8ff', 300: '#90cdf4', 500: '#4299e1', 700: '#2b6cb0', 900: '#2a4365', }, secondary: { 100: '#fffff0', 300: '#faf089', 500: '#ecc94b', 700: '#b7791f', 900: '#744210', }, }, extend: { boxShadow: { huge: '0 30px 60px -15px rgba(0, 0, 0, .25)' } } } } I recommend it to anyone who uses Vue.. since the learning curve is pleasant, like vue's is :] , that's how theming and design systems should be done. Not tumbling thru 10k lines of bootstrap/bulma cores trying to figure out what you can change so you wouldn't break everything ...
Yeh I agree. Having tried out React, Angular and Vue, before choosing a framework, the Vue framework won out for its simplicity and power. It’s documentation is very very well written. Highly recommend everyone giving vue a try.
React is easy to start. It overwhelming at the beginning. Pain start when application start growing. Vue is simple and easy. I personally prefer Angular and Vue. React is a mess.
Yeah, I've been learning Vue recently and it's so easy to learn and get started, I recommend it. I believe more developers are going to feel that same "not fun" feeling with React and move to Vue, making it #1 soon.
I prefer Vue.js too. It's very easy to get start and also easy to grow up with your project. Hope developers who working on react.js could make same works on vue.js too, thank you.
I started with vue and still using it. It was great you can make websites or webapps fast and efficient. Vue will do most of the things for you and the learning curve is not that hard. React on the other needs more configuration and things to learn because it's just a library. But i believe that while both technology can make our coding efficient and also increase our js skills, react has the upperhand in terms of sharpening our skills with javascript.
I'm in love with Vue rn, I've used react sometimes but didn't study it, vue is so easy and simple, it was my first UI framework and won't like another one like I do with vue, but I think I'll have to learn react also cuz most of the market here uses it
Just came from watching a React.js crash course and a Vue.js crash course. I left the React.js crash course super confused vs. what I got from the Vue.js crash course. Maybe the instructor who was teaching React.js made React.js seem harder than what it really is and such could be a factor, but I felt like I learned a lot more within an hour with Vue.js course as Vue.js was so simpler with minimal steps to get the results I wanted. This is why I am an advocate for keeping things as simple as possible!
Was it the Traversy Media ccourses? Brad is a really good teacher. I just think that Vue.js really is that much more simpler or at least I find it simpler.
Yea, I did the same thing. Stated learning React from videos and got really confused. Then I found Vue and the tutorials on it where so easy to understand. React needs all these extra components and the transcribing. Why?!? when Vue can do it all without all that. I am sold on Vue for my single page apps.
For all of those citing React job #s (and Angular job #s) , that's a legitimate line of thought when you are wanting solid, busy work right now. And it's totally true; Vue is younger (not by much, though!) than React, but React had great leverage and market/developer saturation early, with a little boost being a FB product ;-) Also, there is no other framework/library that could come around to be a competing tool better than Vue has done so far. 2016-2017 saw it breaking out and building good momentum, and now at the start of 2018, the conferences being held (including the recent New Orleans conference) have allowed it to really show its growth, increasing popularity, and show others what it can do. My guess is that by mid-2019, job boards and recruiters will be the proof of Vue's growing success in the enterprise, with greenfield start-ups choosing it this year. Other proof of current growth of Vue are the few (though not yet tons of) good online courses available, including the well-rounded and medium-to-advanced vueschool.io and brand-new vuemastery.com. Vue's concept of being "progressive", which regards how you can incrementally use it (script tags in multi-page traditional web apps) or full-on CLI tool for SPAs, as well as going further into server-side rendering and creating SPAs via the Nuxt framework, it provides the community with a wonderful spectrum of gateways. Learning and prototyping simple apps with the basic use of script tags are Vue's own gateway drug ;-) I've never used them, but Ember, Angular and React are all in-f*cking-credible tools for building web apps, hands down. And let's not forget Aurelia, which has some fantastic things going for it! I'll never, nor can I (due to lack of experience) criticize them, and all have their use cases, their places, their pros and their cons. But Vue has some awesome designs to it, including its single file component *.vue format. That, alone, is what makes building full apps, using the CLI, such a graceful experience.
Chris 2018 -> is Vue better than React? Chris 2019 -> Why we should ditch React : )) Since you're using vue, i recommend checking out Tailwind with Vue + CSS Modules(optional) ... the workflow just makes so much sense for a dev who uses Vue... i think tailwind approach to css + CSS Modules is the future ... I actually discovered Tailwind via State of CSS 2019 polls , and the developers Satisfaction and Interest rate of using it was so high, that i had to check it out and wasn't dissapointed. I thought Bulma is so good, but Tailwind is even better. Most CSS frameworks do too much. They come with all sorts of predesigned components like buttons, cards, and alerts that might help you move quickly at first, but cause more pain than they cure when it comes time to make your site stand out with a custom design. Tailwind is different. Instead of opinionated predesigned components, Tailwind provides low-level utility classes that let you build completely custom designs without ever leaving your HTML. Tailwind provides tools for extracting component classes from repeated utility patterns, making it easy to update multiple instances of a component from one place: Button Button Button .btn { @apply font-bold py-2 px-4 rounded; } .btn-blue { @apply bg-blue-500 text-white; } .btn-blue:hover { @apply bg-blue-600; } Tailwind is written in PostCSS and configured in JavaScript, which means you have the full power of a real programming language at your fingertips. Tailwind is more than a CSS framework, it's an engine for creating design systems. // tailwind.config.js module.exports = { theme: { screens: { tablet: '768px', desktop: '1024px', }, colors: { primary: { 100: '#ebf8ff', 300: '#90cdf4', 500: '#4299e1', 700: '#2b6cb0', 900: '#2a4365', }, secondary: { 100: '#fffff0', 300: '#faf089', 500: '#ecc94b', 700: '#b7791f', 900: '#744210', }, }, extend: { boxShadow: { huge: '0 30px 60px -15px rgba(0, 0, 0, .25)' } } } } I recommend it to anyone who uses Vue.. since the learning curve is pleasant, like vue's is :] , that's how theming and design systems should be done. Not tumbling thru 10k lines of bootstrap/bulma cores trying to figure out what you can change so you wouldn't break everything ... (to make your website design to stand out more.. without overwriting and repeating yourself, - well PurgeCSS is useful tool too...)
@@LegendaryJew typescript support is limited in Vue... Especially in SFC templates. Was a big reason for me to switch the react where it basically works 100%
Learning curve aside, there seems to be way more React jobs right now. If someone's getting started and is looking to get work, that might be the most important consideration.
I have heard this at a Meetup of Front End developers - React is big now. Get good at React for a job now. Vue will be big next year (or two). Get good at it for a job next year.
Nice video. I have no experience with React, however, I have developed with Angular 1. When Angular switched to version 2 and TypeScript they lost me. I even went to a one day training with Dan Wahlin and John Papa. I just felt like Angular 2 - 4 became too complex for no good reason. I agree with you about not learning Angular unless someone is going to pay me to do it. About that time is when I stumbled upon Vue. I really like Vue because it uses components without adding a whole lot of complexity. I also like that it is modular and you can add on routing and state management as the app gets a little more complex.
Rico Alexander I don't have problems with react...just don't have time to learn two frameworks. Mostly I picked Vue because I REALLY dislike Facebook. I'm sure it's a good framework.
+sreid70 Believe me Angular 2 is far more easier than Angular 1. My first Angular was 4 but I had to maintain legacy app in Angular 1 and I felt like being thrown to stone age. Maybe Typescript suits me better because I'm native Android developer who works with Java and Kotlin and love to have type-safety.
Thanks for making this video. Vue is the first framework that has actually 'clicked' with me. I also was not a fan of jsx, it just felt...awkward for a lack of a better word.
What I like most with Vue is that it gives you options. It's like a hybrid between React and Angular. In simple cases you just go with templates and 2-way binding, and do easy stuff in an easy way. For stuff that requires more robustness, just go with Components à la React. it even has Vuex which is so much more plug an play than React/Redux, and less boilerplate.
I totally agree with React being the frontrunner. Also the fact that it was "made" by Facebook , kicked in the hipsters and sheep in us. I am a Vue dev and am forced to learn React / JSX / Redux-Saga for a project. After 2weeks of training and online courses on React, It boggles my mind why would I ever choose React over Vue3. the Vue v-if is a no-brainer. And the state as a given and not all those react mumbojumbo setState mutations.
Same feeling here. I started with AngularJS (1.x) which was the first JS framework that brought me into the interesting world of front-end. I was so surprized that I could apply the MVC style of coding in front-end HTML+JS so easily. I loved the AngularJS. When they started re-structuring AngularJS into Angular 2.0, that's where they lost me. I did not pick up Angular anymore. I turned into other JS framework such as REACT but still haven't had a chance to exercise on it, but its "put HMTL into JS" concept bugs me as I really prefer to code HTML in template not the other way around. Vue.js is something I learnt the latest and from what I can tell, I like it. It is very much like the AngularJS (1.x) version but its under-the-hood structure was built with much more mature ground. I think I will use Vue.js as my No. 1 choice for front-end JS framework from now on.
I agree. I started with react, but my new company work with Vue. So i left react and start learning Vue. It is really easy to learn and you quickly get success with it. You do not know, which framework to learn? Then choose Vue, because you will learn it quickly. After that, have a look at react or angular and do some tutorials. After that, it is up to you to move on and became a specialist.
this video was extremely informative and i loved it, I'm a front end developer and i was looking for the low down of these frameworks this done it perfectly, liked and subscribed, brilliant content!! looking forward to more in the future!!
thank you very much. just fyi I have a few courses. www.udemy.com/writing-modern-react-with-typescript/learn/v4/overview www.udemy.com/aspnet-core-web-development-bootcamp/learn/v4/overview www.udemy.com/django-20-for-beginners/?couponCode=CHRISHAWKESDJANGO2
you should know some basics about react. how component renders and state management etc..i would recommend learn basics of freact and its related libraries (redux etc...) first then move to react-native
You don't have to use react at all. Just look at nativescript or vue-native . More importantly, why use Nativescript at all? All native libraries are still restrictive in terms of design and OS version and having compared nativescript to cordova + javascript/HTML/CSS or Ionic 3 I can say that there is very little noticeable difference (if at all) in terms of speed or performance gains when going with nativescript for the vast majority of use cases in terms of html/css UI components. See for yourself. Creat an test app with Nativescript and then create one with Cordova and make sure you have fastclick behavior added for Cordova if you notice a 300ms delay when tapping elements with event listeners.
Do companies use 'create-react-app'? Is 'create-react-app' it suitable for starting big projects? I'm using it, and it is very convenient.. When I think about making a react project from scratch, I think about having to configure webpack and babel.. and it seems like a pain!
I am actually switching to my phone to comment and say thanks Chris. I was not sure but I am convinced that vue is the way to go. I did anather course which required my to learn quite a bit of React. But I wanted to go vue from the get go and during the course I considered React. This video changed my mind. So thank you very much.
Agreed on the point that Vue is much easier to get going than React. Also, you can now use Vue with Vue-Nativescript which is actually nicer than React-Native due to using actual native APIs (this made a huge difference in GPS heavy App). That said I am worried about market adoption of Vue. I never want to be the only one working a framework, because there is always the weird bug you cannot fix or that integration to x you don't have time to build. How do you see Vue's market adaptation? Will Laravel be enough to pull it on mainstream?
Just use a Create-React-App to start with React fast. No need to setup babel and other things. And if you'll need some custom setup, just use "eject". You'll be able to tune your app as you need.
Yes, it can be. And I don't have anything against VUE. I'm sure that it is a great tool. I just wanted to say that fast project setup isn't a case for now for any framework in the list. And in the end, all those frameworks/libs are just tools. I mean, you write app -- not the frameworks.
Simple VUE is a lot like Ractive.js -- easy to work with a adequate for many uses. As an old, antiquated developer, I've seen lots of ways to do things come and go. I feel sorry for companies caught up in the fury of the manager/developers to be on the latest and the greatest. What is popular today is often legacy to maintain tomorrow. Lots of time and money wasted for businesses. It's almost a deliberate conspiracy against companies. Often if applications get as "sophisticaed/compex" as mentioned it is an overkill implementation. Anti-SOLID at the application level. Over engineering has been a software problem for ever.
I have experience on React for over 1 year and Vue for almost 1 year. React is very solid and Object oriented. Vue is an advanced framework that solved a lot of painful part in React and Angular. But I think both of them are very worth of learning. In the future, Webassembly is going take over the development of Frontend. So what ever the framework you use, it would be just a transition.
@6:41 - "these client side frameworks are so complicated these days". I believe in software engineering, it is called accidental complexity. Anyone around still remember how easy it was to develop a simple desktop GUI applications using Visual Basic, WinForms, even C# WPF? How's that someone could spend a day learning Visual Basic and actually could develop a reasonable app, and that was like 30 years ago?
I think the biggest problem with both Vue and React is state. When a badly designed app has complex state managment that is not easy to follow and scattered throughout the app and uses lots of different patterns then it becomes a nightmare to maintain. You have to create components that are unique and that can easily be chopped away or moved into different parts of the app, like a header component that is used across many pages and can be edited in one .vue file for example. And when doing this I think Vue becomes the better tool to use as it is easier and more logical to wire up almost all of the default functionality that most apps will need like state, modular code(components), 2 way binding, 1 way binding, events, dynamic css, transitions. Vue is just a joy to use and it only takes a few weeks of full time use to understand all the features and start using them in production apps. I found myself banging my head against the screen trying to implement things in react that I got working in Vue in far less time. I have 10 years of web dev experience and just have not found any architecture or scope problems with Vue that I could not solve within a day or 2. Vue makes me feel like an engineer again whereas with react I felt like a theoretical scientist half the time.
@ John Smith, Vue event bus in Vuex allows a highly organized approach to even deeply nested child (grandchild) siblings who you wish to communicate with on state changes without changing the state of the parent. There are alot of cool moves you can perform in Vue concerning state management. I am not an expert at Vue, however, I am taking a deep dive to study it daily and build apps using it and goal #1 is to become a ninja in the Vue eco-system which is quite vibrant - From Vue-Cli, Vue-Router, Vuex, NuxtJS, Vuetify, etc.
Great video Chris. The main pain point sometimes with these JS frameworks is picking something that won't be obsolete or lose out to a rival framework 3-4 years from now. It's almost like gambling 😅
Thank you very much! Just fyi I have a few new courses. www.udemy.com/writing-modern-react-with-typescript/learn/v4/overview www.udemy.com/aspnet-core-web-development-bootcamp/learn/v4/overview www.udemy.com/django-20-for-beginners/?couponCode=CHRISHAWKESDJANGO2
God I miss the old days when core JavaScript and jQuery used to be a thing. But ever since React and Angular came along I have been struggling to keep up with its complexity. Maybe I will try out Vue for the sake of simplicity since I am a newbie developer. But from what I know Vue has a small market and much of the source material is in Chinese due to its Chinese background. So I am a bit conflicted if Vue is worth the investment and time.
Polymer is basically a dead project at this point. Its unfortunate because there were some decent ideas in the original polymer spec but then after React gained more traction they decided to try to move it further towards that direction which kind of destroyed the uniqueness of it. That being said, the whole polymer is dead statement is a little divisive. Its still a viable framework to use but only for very specific niches.
To me, hype relates to free technical support. People who are excited about a framework are answering questions, making tools and generally trying to make that thing as good as possible. React has a lot of this, and its had a steady foothold for a while, so its an easy choice for me, bandwagon and all.
Vue has the edge if you are newbie but if you are experienced you should choose react because react has more flexibility. On top of that react does not required you to remember all those directives, syntax, and the 'ugly' path semantics exposed by vuex. But, if you are strugling understanding react with its all capabilities, yeah..... you can pick vue noobs!
Vue is much better in learning curve. I made simple webapp in vuejs pretty easily. And it is like glue you can put exiting project. Im satisfied with using it till now!
I keep seeing references to google search statistics showing that react has more searches. if you actually look at how this works, it's because react is searched for in reference to chemistry or anything else the reacts with something.
Being not a JS Ninja shouldn't be any excuse for not choosing React. I first hated React too but when I really got it!! It really made everything else clearer. React makes you a better JS Developer.
Exactly. Didn't truly learn JavaScript until I started using React and it's a powerful feedback loop where the more you learn JavaScript and functional programming concepts that React is based on the better developer you become. Much prefer knowing what's going on vs the magic strings approach of frameworks like Vue.
As a contractor with 12 years of web dev experience I wonder, if you have spent 2 weeks building apps with Vue and Angular also for that matter? Most React developers tend to really love Vue. I have built apps with all frameworks and for me Vue is certainly the current winner by a long way in terms of clean code architecture and built in features. It's superb. Especially the clean code architecture that you can create when using .vue files as components.
I was trying to learn react for 1 year. A year passed. The framework is complex. I prefer vue. Learning react will take a lot of time and it's actually frustrating and hard to write code for all things..even the routes!
When considering scalability, i.e when our app is growing larger, component based library/framework like React is better. I have enjoyed using React although relatively new with it.
I haven't really messed with vue other than a small tut online thingie.... ive been developing react stuff for a year now for fun mostly and small components for work. You keep saying Vue is for newer developers and stuff...but ive been developing for years and kinda like you i used to love react but i feel like the love is kinda lost now... i have another friend who's a senior developer who used to give react courses he switched to vue for his personal projects and told me it's way nicer to use and was able to build up decent looking SPAs in fraction of the time it would've taken him to do it with react.... I'm seriously considering giving it a try... and like you said alibaba (which is a megasite) and others are using Vue too so i can't imagine it would be bad a scaling up....
Chris can you make a new video about C# .NET or Microsoft overall? I prefer C# over javascript, but everywhere I turn, people are saying microsoft is dying and that they hate/avoid using MS Windows. Is there any truth to this? Because soon I am going to apply for a job and I don't want to be working with a "soon to be dead" technology.
to get a job you can't go wrong with react. I went to a big tech career fair in SF and asked recruiters what is the 1 most important thing they are looking for and it was always get a project on your resume with react. react must be on your resume front and center, bold, underlined, 15 point font. even for some smaller positions and projects that weren't just straight up front end web development said that react will push your resume up the most.
That maybe true but there is a reason for it's popularity with companies. It's functional concept and component model is the best most powerful one out there.
What about create-react-app? That should have dumb down the setting by a whole lot. You can create production apps with it. And react native is a big plus on the react side. I agree with the Angular part too, unless someone pay me, I will not touch Angular now. Heck, by the time someone pays me to learn Angular, it'll probably be Angular version 13 or something lol...
+Emem Umoh Framework is usually a name reserved for a library that encompasses your whole app. Like Angular, even if you have you domain specific code you will have Angular imported so you can register your services and stuff. Vue and React don't provide a way to solve non-UI problems and they are just UI specific.
Vue is much easier to learn, I used to write vuejs code in some small projects, but if you wanna dive into a big project, React is definitely the right choice, since the much bigger ecosystem.
That's not really true. It really goes down on how u implement Vue with big projects. We are working a humongous project with multiple backend architecture for both MVC and Web API in .Net Core 3.0 and I can tell u right now it's even more easy and organized to maintain the codes using Vue on the frontend. The fact that the Vue is the fastest component rendering reactive javascript framework as its component comes with the three layers in one component is a game changer. React JSX allowing the mixture of html and css in the script is the biggest garbage I've ever seen. On the other hand, overkilling framework Angular is a waste of time. A biggest bullsh*t technology we've used forcing to be like a backend style MVC approach on the UI client is just overkilling non-sense idea. When our team discovered and learned Vue. We completely ditch everything and just focus on using the Vue for the frontend stuff.
No offence to any React and Angular developers, but I'm hoping more work on Vue would pop up soon. I've chosen Vue as my first JS framework and absolutely loving it! but most of the employers just want React devs :/ . Personally, I feel that Angular is much closer to Vue than with React. It took me sometime to get used to React and Redux
Thems fightin words. But I actually have a serious question. Given that FB stock has plummeted since the Cambridge Analytica leak, do you think this will inversely affect the continuation of React or jobs that require React? Will it become less popular because the thing it was known to build (for the most part) is now under scrutiny by the likes of even Elon Musk what with the latter deleting his fb? Would make me switch to Vue.js or Angular.js if it ever came to that.
No, React is no longer a part of Facebook it's gone open source a long time ago and is now under a MIT licence, it's the same with Angular, backed by Google, but not actually owned by it.
The two of the largest e-commerce websites, wal-mart and alibaba, use vue. People who want to make money need to learn how to build SPA on vue. React is on its way out. React has a lot of broken modules. Every week, your code breaks because a third party developer for react decides an api needs to be deprecated. Dog chasing its tail. I had a project started out with React, we spent 2 months trying to get out website out, then along our development a node modules broke, and its 4 months later, we couldn't get the website done. So we scrape React, our developers hate React with a passion, now we are using Vue in production only after 1 month of development. React core developers are the dumbest people on earth.
Just fyi I have a few new courses. www.udemy.com/writing-modern-react-with-typescript/learn/v4/overview www.udemy.com/aspnet-core-web-development-bootcamp/learn/v4/overview www.udemy.com/django-20-for-beginners/?couponCode=CHRISHAWKESDJANGO2
You say that but as a contractor having to reverse engineer React apps is a bloody nightmare. I have no intention of working on another react project ever again unless it is a greenfield project. There is a reason why react pay has doubled in the last 2 years and i can tell you that this is not good for businesses but its great for react devs :D . React is such a terrible idea for any company to use on projects starting in or after 2018, and the basic premise I give is that if you don't mind spending a fortune on developers and making sure their every need is catered for so they don't leave the company and force you to code everything up from scratch then yea go for it and use react otherwise use vue and make sure you create well architected and simple code that new developers will be able to come in and understand and contribute to.
I know nothing about React, Ive never tried it. Vue has been a good tool for me and it seems to do the same job as the other 'libraries/frameworks(whatevs)'. Honestly though I was learning AngularJS for 6 months before it was shit canned and I thought it was awesome. As far as Jquery, I liked it a great deal too, I would still use it any day(I found its syntax easy to work with as long as I didnt nest too deep with it.).
I think dude knows what I mean, nerds like this in the Linux community too, lying in wait bent on correcting every little thing they can to make themselves feel smart.
React is something you use if you don't want a over opinionated solution, it allows you to build and grow as you see fit, also I have yet to see a more elegantly way of handling components, also its speed.
2 years ago I started with React/Redux and it was good a better experience than Angular 1.x but I did not like JSX it tends to clutter your view I used it for 5 months then I tried Vue, .vue files are amazing encapsulating js, css and html in one file makes a win. React has more tutorials but *Vue docs* are way better than react
Have to disagree, React has far better component handling, also if you've been using React for two years, you should know that you're meant to separate your smart and dumb components, also styled-components make CSS easy and modular with having to initialise the component like in Vue., if there's one thing Vue is good for it has more tools, so if you don't like browsing for tools it has your back, but then if you want all inclusive framework than Angular 5 is the way to go.
So if you're working with crappy programmers, choose Vue. Got it. ;) Me I'm choosing React because I want the power of JavaScript with my html code(JSX) that I'm writing and don't want to use a magic strings templating language. Just give me JavaScript and leave me alone. I'm not afraid of it. I love it.
