Angular, React.js or Vue.js? I get this question a lot! Let me share some thoughts on it with you!
Early bird offer - Join my course on this topic for only $10: https://www.udemy.com/angular-reactjs-vuejs-quickstart-comparison/?couponCode=YOUTUBE_PROMO
Introductions to all three frameworks + detailed comparison included!
Want to dive deeper into React or Angular or Vue?
React - The Complete Guide for only $12: https://www.udemy.com/react-the-complete-guide-incl-redux/?couponCode=ACAD_YT
Angular - The Complete Guide for only $15: https://www.udemy.com/the-complete-guide-to-angular-2/?couponCode=YOUTUBE_2
Vue.js 2 - The Complete Guide for only $15: https://www.udemy.com/vuejs-2-the-complete-guide/?couponCode=YOUTUBE_VUE
JS Framework Benchmark: https://github.com/krausest/js-framework-benchmark
You can follow Max on Twitter (@maxedapps), like us on Facebook (https://www.facebook.com/academindchannel/) or visit our Website (https://www.academind.com).
See you in the videos!
Lastly, I think a library that doesn't ship with more doesn't exactly make it worse. Sometimes this can be more of an advantage than not. Case and point is state-management. Angular's state management uses Zone.js for under-the-hood dirty-checking, so the amount of re-renders is often times extremely inefficient. React avoided implementing more than they could get right, and thus Redux is present, and although is pain in the ass to use, it doesn't cause needless re-renders. Vue happens to be a case where they shipped state management AND got it right, so the rule that shipping less is better isn't a set in stone rule, but shipping less is better than shipping more crap.
Hi, I just Install React 16.5 version but I'm confused because I'm not able to config the eject for CSS. I'm waiting that you tell us how to config the new version of react and eject and also I'm getting some console Debug error Thank's
Angular 4 in front, Express in back , MongoDb , Node ( they're the best , fastest, most secure, compatible with each others ) .. Don't use React - Ever - guys .. having said that -> You can use Vue but only in small projects, it has some security holes thou !! ..
One of the reason react is so popular in the uniformity in jsx when working in development teams there are many ways to code and its not always easy to understand each others code. The jsx creates code patterns which speeds up production and development time
bro i m confused so much what should i learn Angular , React or Vue . i was thinking abt Vue finally then i think to react . i saw ur video last night i m going for angular . i am thinking for vue again . i m very confused lol . plz help . telme one framework , what is best n helpful .
In the end it really depends on the project and your personal preferences. Maybe the updated version of the video or the corresponding article help you to make a decision here: https://academind.com/learn/angular/angular-vs-react-vs-vue-my-thoughts/
I am a fan of JSX, but you brought up a good point -- HTML and CSS already exist. That said, I prefer JSX inline compared to using directives and magical attributes on vanilla HTML. React is worth learning, it's really easy once you get the hang of it. It is more elegant and easier to think about than Vue and Angular, in my opinion.
Been using React for almost a year now and all I can say is that React is more focused on SPAs and only SPAs. While Vue looks like you can drop it into any existing project and add rich functionality to it.
Can anybody define and explain a bit or share some link on two of my questions plz _- 1) what does development framework has to do with a Router? (2) what does development framework has to do with network connection type/speed (3g/4g) etc ?
And im here and not a fan of any of these frameworks. Vue.js is the best for what i need but angular is absolute horseshit, I just do not like a single thing about it. From the routing to the services to the way we need to use typescript, its just bad.
For writing apps that work on phones, tablets and desktops... Google's Material Design is key. I have had trouble with Vue and Material Design. Just now, React seems to be the library of choice for aws... especially AppSync. Together with Material Design, Application STATE is the 2nd over-arching pillar of front-end design... but... how can a pillar be over-arching?
Hey Max, I've bought many of your courses on Udemy... including Angular, React and Vue. And have a comment... I liked Vue, but the mobile part is very infant yet, however in Angular you have Ionic and in React you have React Native. So only for that I will not invest too much in Vue. I'm still split between React and Angular. In my company we use React most of the time because is what we do better, however Angular and Ionic are very tempting, specially since is a hell lot easier to build the CSS and actual HTML.
> complain about made-up names like className, onClick
> Use HTML and CSS instead of re-inventing it via JS.
I actually got nothing against React by the way - JSX just isn't my favorite way of working with the DOM. Templates + directives don't have to be yours
For Your kind information React is a library not framwork.
You are considering React as a framework and thats your downpoint when you start considering as library you will definiately love it . <3 <3 <3 <3
I'm not a fan of JSX and that won't change depending on how you call it. But I got an updated version where I pay great attention to the semantics ;-) => https://academind.com/learn/angular/angular-vs-react-vs-vue-my-thoughts/
I played around with it a bit but never used for anything but very simple apps. I guess its nice if you need the smallest possible bundle but I can't judge at which point React wins when comparing runtime performance.
Putting a transpiler atop an interpreted language obfuscates and abstracts-away what is happening in the code. They add arbitrary and often poorly-chosen "magic" keywords and symbols into the code that are different from anything else. In Typescript - the syntax is almost as bad as the old Objective-C Apple inflicted on us back in the 1990s ( nee Next 1980s ). Holy crap it's bad. Question marks for "anything can go here" - which COMPLETELY breaks one of the alleged reasons to add the complexity of TS in the first place: strict typing. It's basically a c++ style "cast" statement which became a shortcut for "I don't have time to fully flesh this out, so eff-it I'll just stuff this here and deal with it later." It also breaks the form-validation that you seem to obsess over.
Also, the modularity of TS - especially in Angular 2.x+ has become a nightmare ( in my opinion ) - The "components" ( with all kinds of magic files and incantations ) - and the templates ( harder to use than AngularJS ( 1.x ) aren't any better OR SAFER than what they replace. In fact, they are harder to use in some ways than the ng-include they replace.
On a slightly different issue - the fact that Angular ( in particular ) keeps updating and radically changing their framework makes it unusable for a production website. It's just too fragile, and too much of a pain to try to keep-up with whatever fad the team is seduced by seemingly every month.
I see your point but I think TS is actually a huge improvement over JS => It makes development much less error-prone. But obviously, you can pick the solution that works best for you and I can understand if that's not TS
Typescript is great. I think what sent everyone screaming initially with Angular 2 was dart. Typescript is really just JS with Static types, and static types means better stability and an IDE able to static analyse things to make really helpful autocomplete. Dart was a straight up new language. But I'm definately on team React these days and JSX is absolutely a new language, of sorts.
Hi Max, thank for all the videos. Offtopic, but do you plan to make Laravel ot WP-API course? You helped a lot of people level in front-end, can you do the same for the back-end? Laravel and Lumen + Vue courses would be great.
Great to read that you like the videos, thanks a lot for sharing this! Currently I do not plan to create such a course in the near future, I might create other Laravel videos here on the channel but that's also not something I can promise right now.
Well, for me the key feature React and it's eco-system offer is the ability to properly manage the state of the whole app thanks to the fact that React promotes writing things in a declarative manner.
Being sure that all the data you need is (or at least is supposed to be) immutable and you can actually rely on it without expecting something to break, just means a lot to me.
I want to learn vue.js (Thinking about this course: https://www.udemy.com/vuejs-2-the-complete-guide/#instructor-1) to write a web client for my backend rest api. (Why vue? Why not ¯_(ツ)_/¯?) Never worked on frontend before though. Do you know of any courses, free or not, in form of text, videos or a book, doesn't matter, through which I could gather all the necessary knowledge on html/css/js to start learning vue.js?
I've worked in Vue and React (not Anguar since 1.x) and I prefer Vue simply because of the separation of concerns. While your code in Vue will always be logically separated (unless maybe if you use JSX with Vue, which I have not), React can turn into spaghetti code real quick if you aren't careful.
How about they all suck. Let's face it at the end of the day, you're still stuck with a crappy looking HTML web application. In particular, none of them can produce full featured graphics and are trapped within the CRUD paradigm. They will also only support the most basic coordinated animation capabilities. These shortcomings are obvious, so why do all web developers nod their heads in unison and chant "HTML5 rocks!!!". Its like conversing with a bunch of brainwashed automations.
Totally agree on the ES6 part but not everyone is just getting started with JS. Believe it or not, I get questions like "What does 'let' mean?" a lot and hence any assumptions on ES6 being the standard for everyone are wrong. Does of course not mean that a library/ framework/ whatever-you-want-to-name-it using ES6 (or strongly benefiting from it) is bad.
Regarding the "Library vs Framework" thing: What do we gain by differentiating? For learning React, this doesn't matter. For comparing Angular and React it doesn't either. But yes, you are right, it is a library.
1) You woudn't call jQuery a framework, does you? Nothing is bad about letting students know that "while react is technically not a framework, it solves the same sort of problems so can be compared to Vue and Angular". Thats instantly gives wider vision on existence of different architectures and existence of architecture at all, and thats sounds good for me personally.
2) I am only assuming that ES6 is not a "pro prerogative", but almost minimal requirement for js developer in 2017-18, especially concidering very small amount of actual changes in the language between es5 and es6. ES6 takes literally couple of days to "learn" if you already familiar with ES5 JS, so how learning it can be con of the framework/lib?
1) Yay! Religious War! Seriously - people choose between React, Angular, Vue - I guess you get the point of the video. ;-)
2) Why are you assuming everyone's a pro? If you're diving into web development, you'll still see a lot of ES5 code. Obviously, ES6 is becoming the new default but don't act like it's the standard for everyone already. Besides - the video was recorded over a year ago.
It is but I'm not a fan of these "definition wars". You use it as an alternative to Angular + Vue and if you add react router and redux (which are NOT part of it, I know) you get a similar set of features. This is how people use it (for SPAs), this is how I talk about it ;-)
React is combing designer and developer profile , and making everyone a full stack developer. i think thats the future. Cause designing is something , that doesnt involve huge skills , you get stock design components online, and you just have to edit them. no one designs everything from scratch these days. However development needs logic , what logic and framework you apply , it totally depends. With React you can use firebase / node / jquery / etc etc. its a plithora of library . and it gives you a lot of freedom , to do things in a 100 different ways . which is why i would vote for React and Vue , however vue is something i havent implemented much.
You are so wrong here bro :) .... Did you forget about pre written libraries developers use ? Or the code snippets from stack overflow ? Designing is as hard as developing if you know what good design is! Which only a trained designer will know. I am from India and it seems you are too(but I might be wrong) that's why I know due to the Engineer / Doctor mentality we have less regards for design courses and designers. To be honest that's not just you every developer in India thinks that. Try to broaden your thinking and then you might realise designing a good product (here app/website) is equally difficult. That's why seasoned developers in with no regard for designers create ugly apps or websites coz they are never trained in color theory, design rules, good ux design etc. You can see endless examples of this with a simple Google search.
Been working with Angular for the last month and would have to say its all logistics. The scalability of angular is overstated, you can create a backbone application more modular than that what angular can give you. With a good understanding of modular / component paradigms, you can have less points of reference through large applications with backbone / vue.
Also many teams that use angular, use it as an excuse to write terrible code. Working on application at the moment that when registering a new component, you need to edit 10 different files, excluding the component itself haha. I look at my past applications every couple of days to relieve stress.
Man this makes me sound like a dick haha.
Two way data-binding is a myth lol.
Academind, thanks, finally, a good, sane comparison out of all other comparisons, that I have seen. Your video has helped me to choose the right framework to learn - vue. I also prefer the separation of pure html, js and style.
I think your bias to Angular... JSX gives you cleaner looking code. You have reuse stateless components. React is the quickest as well because it is only the V in the MVC. Vuejs is really cool though, if you want to build quick, use VueJS. The only problem is there is no support for it really. There is only like three plugins for certain things where if you choose React you get TONS of options.
I always love your informative tutorials. I would like this too if you discuss here about Making a SEO friendly web app. Which framework will be better for making web app SEO friendly. I know about server side rendering in Angular and Vue might be in React too.
But I found server side rendering in Angular is very tough. Third party library like ngx-bootstrap, facebook sdk etc break the server side rendering in build step. Also found slow performance in initial page loading etc.
I would be very very grateful to you if you explain comparatively which framework is best for making SEO friendly and easy integration of third party libraries.
I enjoy your videos. I would be interested on your thoughts on this same topic now that its over a year later. I am loving Vue right now but I'd be curious to hear your findings a year after making this video.
Havent used vuejs yet but i have to say that i prefer angular as my code is easy to keep organized. Everytime i have to use react i hate it because the way things work with react it tends to end with messy harder to maintain code thats smells really bad. Maybe that comes from my c++/c# background though
Angular has become painful with every version released, react is cool, jsx isn't that bad even people criticize it the most while being asked to give an opinion about reactjs, but VueJS is nothing compared with these two, easier, well documented, and fun to work with! Facts are facts.
Even though I obviously like it because I'm the creator, I would argue that my course is the most comprehensive and complete course you can get there => https://www.udemy.com/the-complete-guide-to-angular-2/?couponCode=ACAD_M
The problem is not that Facebook and Google are the only advertising platforms. The problem is that they are considered mainstream media and without these two, the trend of cryptocurrencies gaining legitimacy is delayed. That is right, I said delayed not blocked or prevented.
The World Has Changed.
Five years ago, when bitcoin was unknown to most people, this might have been a fatal move. Today is a different story. I recently traveled to a remote mountain town in the interior of Mexico. Everyone I met had heard about Bitcoin and eyes lit up with excitement when I ask if I could pay for lunch with bitcoin.
Today are dozens of websites dedicated to cryptocurrencies, either holding them, exchanging them or just writing about them. Probably the most effective advertising remains on Google, it is called Google Search and it is free.
If someone wants to learn about owning bitcoin or any other currency, there is a ton of educational information.
The Flipside Is Being Ignored.
Not All Regulation Is Inherently Bad.
If we examine the full spectrum of regulation to this point on a global scale there is one common target most everywhere. That is the practice of exchanges. So far there has been little or not regulation, threatened or enacted, to protect investors from loss of funds due to security breaches.
Capitulation Is A Good Sign.