React, Vue, && Angular, OH MY!
0:00 / 0:00
React, Vue, && Angular, OH MY!
Shout out to our sponsors for supporting the LadyBug Podcast!
Difference between a library & a framework - 1:04
Do we even need a framework? - 4:37
Pros & cons of using frameworks - 13:25
Popularity of different frameworks - 16:54
React - 25:31
Vue.js - 34:14
Angular - 39:34
Which framework is right for me? - 44:23
Evolution & speed of frontend development - 45:44
Learning these frameworks - 47:31
- JS Frameworks Popularity
- History of frontend frameworks
- Tyler McGinnis React Hooks Course
- Pure React by Dave Ceddia
- Introduction to Vue by Sarah Drasner
- Evan You
- Wes Bos
Particpate in Hacktoberfest!
October means Hacktoberfest! We released two episodes (Part 1 && Part 2) on Hacktoberfest last week and we’re participating! If you see a bug on our website, feel free to open a PR with the fix, or check out some of the open/available issues here! It’s a great way to get your first open source contribution!
Help us out
Ali 0:21 I’m Ali.
Okay, so let’s get started here. One of my favorite questions that I think I’ve asked Ali probably four times already is, what is the difference between a library and a framework? Because I can never remember.
Yeah. So a library is generally a set of functions or methods that somebody else wrote that you are including in your own code in order to make it so that you’re not reinventing the wheel or anything like that. So the library is pretty flexible. You’re just importing stuff using other people’s code. Whereas a framework generally, it changes how you structure your code. So something like Angular, which we’ll talk about today, there’s a specific file structure and way of writing your code that’s very, very different than if you were not using Angular. So it’s not just a bunch of functions and methods that you’re adding into your code. It’s dramatically changing how you’re restructuring your code. The fun thing with frontend frameworks is that there’s a bunch of debate whether these things fall into frameworks or libraries. So generally, it said that, like, React is just a library, not a framework, though, if you use something like Create React App, I would argue argue it goes more into the framework side of things. And so I think that that is an interesting conversation to have. And definitely something that a lot of developers definitely nitpick about. Whereas I, I don’t know, part of me is like, yeah, semantics matter, these names matter. But then also, part of me is like, does it really matter if these things are libraries or frameworks, and they all kind of fit in the same grouping of what they do and like how they matter and change the way that you write your code. So maybe we just need a new name for the set of libraries or frameworks that allows you to write component based applications or whatever,
That’s really funny. It’s like, anytime you post about React, being a framework, you get 1000 people like “React in the library. React as not a framework.” And I just like, it’s just… it cracks me up because I know I’m going to get those comments every time because like, technically they’re true, but I would agree that maybe we should just change the wordchoice here, because they are tools that help you build applications. And there are a lot of similarities between them. I think I read something somewhere where that was saying like frameworks are opinionated about the way in which you write your applications versus libraries don’t have that opinion. So they’ll give you you know, a lot of powerful tools and functionality and whatnot.
I think at the end of the day, whether you call it a library or a framework, and again, this comes from the person who can never remember the difference, whatever it’s called, it doesn’t affect my ability to use it. And I’m able to use it, whether I call it a framework, or I call it a library.
Totally. And I think like React, even though it’s a library, it’s so dramatically different than something like Lodash or D3 or something like jQuery even. And so I think we do need some sort of name that groups all these things and it’s become vernacular really like frameworks, but that’s not technically correct. And so I think that’s where the issue comes in is maybe we need some new like…
Ali 4:01 name for for the UCF
That’s how we fell into the trap of calling HTML a programming language.
We don’t even want to open that can of worms.
Ali 4:08 Taht’s a whole other debate Kelly.
It’s my favorite thing to tell people.
I only write CSS.
We’re gonna make Twitter really angry, right?
Emma 4:17 That’s ok.
It’s what we’re here for.
So for the purpose of this conversation, I’m going to probably just stick to the word framework because it’s easier, and it’s less syllables that I have to spit out of my mouth. So… but don’t be offended. I’m not trying to exclude any libraries over here. So that kind of leads into the next question, which is why do we use frameworks? Do we even need frameworks for applications? And like, why do they help?
I thinkthey can also just make programming fun.
Ali 5:35 Totally
Kelly 5:36 That’s been my most recent experience and learning Vue in the past month is just… I’ve haven’t had this much fun coding in a very long time. So do I really need to use Vue or do I really need to use React? Probably not. But I’m going to anyway just for an excuse to learn and just because it’s fun.
I completely agree. I learned jQuery before I learned vanilla JS. It really threw me off when I had to not use jQuery for projects. And I’m like, Oh, that’s not gonna work. Oh, that’s not gonna work. What is this dollar sign doing here? I should probably remove it.
Yeah, totally. Everybody’s gonna learn differently. And that’s totally valid. I just personally wish that
That’s exactly how I learned. I learned from a book.
Emma 11:36 Did you? Oh gosh.
Emma 11:50 Oh, I love that book. The one with all the pictures? I loved that.
Kelly 11:52 It’s a great book. Even now that’s still a really great resource, not that I’ve touched it in a really long time, with… at least the cover’s pretty.
Yeah, and the HTML and CSS one’s great too, because there’s a lot of visual graphics inside. So we’ll link those in the show notes.
They’re great. I don’t know if you’ve used them recently. But they first of all, it’s actually not Code Academy, at least the URL isn’t. And I feel like what is that the Dunning Kruger effect? Where like you think something is one way your whole life? And then you’re like, what it… what do you mean, it’s not tostino? It’s tostitos, or whatever. But I always thought it was Code Academy and you type it in its Codecademy? Yeah. Anyway, that was a tangent. But my point is, I went back to them like recently, within the last month or two, and they’ve upped their game. I mean, they used to be like, just entry level like, you know, I that’s how I learned Python back in 2013. Now, oh my gosh, it is so much better of a platform and they have learning paths now. And we’ll link that too because I loved that site.
Definitely, it’s really important to think about that, especially the whole world. And so many users are in India and Indonesia and other countries that definitely have lower speeds than we do. And in addition… or we do in the United States. And then, in addition to that, people using smartphones that aren’t at the same speed as the iPhones or Google, what are… the Pixels? That’s what they’re called.
So definitely just thinking about everybody’s on a different device and thinking about the whole entire world, not just people who are in perfect situations as far as speed goes. Okay, cool. So we’ve been talking about all these frameworks kind of generally, but let’s start talking about specific ones. Emma, you want to talk about how popular different frameworks are?
I wonder if that has anything to do with the fact that it’s thanks to Facebook?
I do think that, and we can talk about this a little bit more, but essentially, React is backed by Facebook, which essentially, you know, I think that was a big leap, right? Versus you look at something like Vue, which is, again, still in its infancy. It was just released in 2014. And it’s, I believe, it’s open source, if I’m not mistaken. That’s not being backed by a big company, whereas you got Angular. AngularJS is backed by Google and, you know, React is backed by Facebook. Vue, is doing its own thing independently. So I wouldn’t… Yeah, I would guess the the association with Facebook, the backing by Facebook was for sure one of the reasons it took off.
I think so too. I think another piece of it is the community that’s popped up around it. I think that those are kind of self sustaining in a lot of ways to. So let’s talk a little bit more in depth about React because we’re talking about it now. So it was released in 2013 by Facebook. Have you all been using React for a while? I feel like…
Emma 20:21 Yes.
Kelly 20:22 A while? No.
Emma 20:25 Well, yes and no.
Like, this year.
Yeah, so my history is starting with AngularJS back in the day and dealing with all the debugging fun with all that. And then we quickly moved over to React. So I’ve been using React since 2015. jQuery in there as well, important piece of web history and still out there. So shout out to jQuery. And then from there moved to Vue for another project. So I’ve been using Vue for a decent amount of time as well, probably 2016 or so. And then, when I moved to teaching, I teach React. So definitely have to know it pretty well for that, and then also have taught Angular periodically as well. So that’s a little bit of my history. Kelly, how about you?
Sorry, I’m going to jump in just because I remember using AngularJS back in the day, and like the model view controller paradigm, like destroyed my brain, like I sat there and I was like, I don’t… how do I even use this computer? I don’t understand it and I don’t know about you, Ali. But like, I did not like AngularJS.
Oh, I am totally on the same page. And the debugging for it was so hard. It was before, like, the dev tools came out that made debugging React and stuff so much better. And oh, my goodness, debugging AngularJS was the narliest thing I’ve ever dealt with. Then the whole ecosystem at that point to was like, Grunt and Webpack and you had to write your Webpack config yourself and before Create React App. Just those days of frontend development I don’t miss whatsoever.
That was a part of my career where I would just like copy pasta, like all this code, from the internet into my Webpack config and just be like I think it works, ship it.
That was literally my life. Yeah. Or like I had one previous project that worked just fine. So I’m like, I’m just going to keep on reusing this and I don’t know what any of it means, but apparently it works so I’m going to stick with it. But yeah, I also started with AngularJS A long time ago, and it completely intimidated me, just like I’ve explained. And so I didn’t do anything outside of jQuery until last year. And of course, I’ve been in a very small box as far as what kind of things I’ve been building. Basically, since 2012 most of my experience has been building WordPress sites for clients, and then building Shopify stores for clients. So, you know, I’m not kind of exposing myself to the various opportunities to learn other frameworks just based on what I do for a living. So I started learning React earlier this year just for fun for my own personal site. And then I started learning Vue a month ago for a client project and I had to learn it very quickly, but I figured it out. So there’s like a, I think, like an ah God, I don’t know many years, like at least a six year period where I was just like, asleep on all the frameworks. I did not do a thing with any of them.
I think that’s awesome, though. I think that there’s a lot to be said for that and staying stable with what works and just using what works instead of using the new shiny thing. I think looking at how you young these things are is actually really fascinating for me. I was prepping for an interview on like the history of React and was looking at like when Redux came out and I realized that I was using Redux pretty much when it came out and that was just fascinating to me. I was like, Oh, I had assumed at that point that Redux was just around but nope, I was pretty much using it like couple months after it came out. And that’s that’s wild to me so…
You’re such a trailblazer.
I know it’s wild. I had really bad shiny object syndrome for a very long time, including writing apps before there was an English translation of the docs for some things, so I was using like Google Translate from Chinese for a framework at some point. Anyways…
I think it’s really fun when like you learn a new technology because I had to learn Redux too and I remember my mind turned into jello for a solid, like, two months. As I was like what is an observable? What is? Well, that’s RxJS. RxJS has observables, which also like boggles my mind, but Redux… I was like, what is a dispatcher? What is a reducer? I don’t understand. But then once you learn it and it clicks, you’re like, I’m gonna use Redux in everything I’m going to build, you know, a single page application that has only static data and there’s no reason to use Redux. But I’m going to use it anyway. Because, you know…
I just want to make one quick comment. Just to add in here for people listening who did not understand a lot of the words that Emma just said. Don’t worry, you’re not alone. I don’t… I don’t know them either.
Emma 25:24 Funny, I don’t either.
I like to think of components almost as like a rubber stamp where you create the stamp and then every time we need one, you can physically just stamp it like you would do if you were, I dunno, stamping a bunch of paper. I don’t know why you would do that. But that’s how I like to think of them.
Ali 27:04 I love that.
That’s what Emma does in her spare time.
I do. I’m a professional stamper.
Stamper of React components.
What I find really interesting about React and this took me a very long time to comprehend is this concept of the virtual DOM. I… it still today, like, kind of blows my mind. So it goes back to this concept of like, what is the DOM, right? And we can think of the DOM is an object-based representation of your HTML document, as well as the interface to manipulating it. When we think about the virtual DOM, what’s the benefit here, right, we want to solve the problem of like, needing to frequently update the DOM in a more performant manner. And it’s… what’s interesting is it’s not an official specification, it’s really just a new way that we can interact with our DOM. And so we can think of this almost as like a copy of the original DOM that we can manipulate and update without having to use the DOM APIs, which makes this a lot more performant and optimized. And so once we’ve made all the updates to the virtual DOM, at that point, we can say, Okay, well, these are the changes, we know we need to make between the virtual DOM and, you know, the actual DOM. Let’s just make those, and this like, revolutionized the way in which we build our applications, because oh my gosh, there’s just so much more performant than, you know, having to change the DOM every single time.
Totally, totally. And this also goes back to that idea of like perceived performance, is that the way that React updates sites feels really fast and feels really smooth. And so that can make the site feel faster than it actually is, which is another interesting piece of all this. So I think component-based architecture, virtual DOM, I think that those are the two big pieces of React that… they’re huge for react and huge for that piece of web development. But in addition, those concepts have kind of boiled out to the other frontend frameworks that are out there as well and have just kind of revolutionized the way that we write code even outside of React. So I think that that’s a really interesting piece of all this as well. And the other really huge pro of React is it’s huge ecosystem. Like, I feel like so many people that I follow online are React people and talk about React all the time. And that’s, I feel like why I talk about React less is because I just don’t want to compete. Because there’s so many, but it’s got this massive ecosystem behind it. And that makes it really friendly to learn and also means that there are tons of libraries out there that you can use in order to extend your React applications.
this.myFunction = this.myFunction.bind(this), and that was pretty frustrating. And that introduced this idea of class fields, so that we could do like
class myComponent extends React.Component. And so we went, you know, you haven’t used createClass now using React.Component. Now we get into class fields, and then just recently is where hooks have kind of come into play. And there are many benefits to hooks, you know, we don’t need to go into all of them. One of the main benefits is they allow you to have local state in your components. They can be persisted across renderers. You can, you know, say like, my sidebar is open, my sidebar is dismissed, and it can persist across rerenders. And instead of using, like lifecycle events for different React components, now you can use… group by logic, so there. That’s like the very high level timeline of of how we got to where we are today with hooks. That confused me for a very long time. I never understood why, like, I saw some people like not using
this.state equals object within a constructor, but they were just declaring it inside the class`, like that had confused me. And I want to give a shout out here to Tyler McGinnis, his React hooks tutorial, because that’s how I learned. He walked through those those steps. So.
Before I talk about Vue, I do want to ask a clarifying question for people listening and also for myself. Can you explain the difference React and React Native?
Yeah, React is used to build web applications in a browser versus React Native, from what I understand, is used to build mobile applications for both iOS and Android. Because iOS in general uses Objective C or Swift to be built. And this can be really hard for people who know, you know, who only work on frontend browser… in the frontend browser to work on mobile. And Android is built with Java, if I’m not mistaken. And so React Native allows you to build one application that can be served on both, if I have that correctly. And it’s it’s not the same exact syntax as React. It’s quite similar. It seems like it’s not too hard to pick up, but I’m pretty sure that’s the difference.
That sounds right to me. And then I think you can use it to make desktop apps now too or something. I don’t know. mobile development is way outside of my real
Right. But I think the whole like… I think it’s React Native because it’s used on like native… for native applications on your devices.
Okay, it didn’t like the the newest Mac OS update, like Catalina or something, make it so you can use it to build, like Mac apps as well. Am I making that up?
I think so, something along those lines.
Okay. I don’t know. I don’t I don’t work in that space. So it’s all gibberish to me. Okay, so let’s talk about Vue. So Vue, as we covered before, it is not backed by a, you know, a popular organization like Facebook. It was created by Evan You who was an ex-engineer from Google. And he created this back in 2014. And similar to React, it also uses the virtual DOM, which I think for me, I learned React before I learned Vue so it did make the transition to learning view a little bit easier. And honestly, that I think is one of the biggest pros. I think it’s a very easy to learn compared to the other frameworks out there. I feel like the learning curve is a lot lower. Did you have the same experience with that?
Just a couple of fun facts about that. So from what I can tell, Evan You said that he he basically wanted to extract the parts he really liked about Angular and build something really lightweight. And another quick like fun fact is that, if you haven’t noticed this, Vue’s releases are codenamed with anime names. Because I guess Evan’s really into anime and manga. So that’s a fun fact.
That’s a very fun fact. So one of the things I think that is also really great about Vue, know, also in line with React is the ecosystem. When I started talking on Twitter about, I’m now starting to learn Vue, I had so many people reach out to me and be like, use these resources. These are really great. Ask me any questions that you have. And in you know, I’ve hit situ…, you know, certain situations and trying to build out this, this PWA for a merchant, where I don’t really have that much time to really sit down and learn it. And these people have been so quick to respond and answer my questions like, this is how you should code this stuff. And it’s been really helpful and I think the the ecosystem around Vue is wonderful.
I do find the Vue community to be so wholesome and very welcoming. And it doesn’t feel like there’s any, like, competition to prove anything there. It just seems… And I’m not really sure why that is. But I personally feel very welcome in that community.
Yeah, agreed, agreed.
And I think also, it’s kind of a pro and a con. It is newer, as we’ve discussed. And with learning something new, or just using something that’s a bit newer to the space means that there’s a little bit less documentation available, although the documentation for Vue is great. Like literally just like the Vue website for it is wonderful. But also, with a, you know, a newer framework, it’s going to change over time, and things are going to become deprecated and there are going to be some breaking changes. And that’s, it’s the nature of using a newer framework. So it will require a little bit of following along with the changes that have occurred over time.
I feel like that goes to any framework or library there too, because if we look back on the history of React and Angular, let’s not even talk about that yet. These things change rapidly, regardless of their maturity. And so I don’t think That should be a detractor. I would agree with what Ali was saying about the fact that, and I hope I didn’t like misunderstand this, or misinterpret this, but I personally feel like Vue is a little easier learning-curve-wise to get into then React. React is… it can be a little bit more convoluted. Vue is very simplistic, it seems quite user friendly. And if you’re on the fence between the two and you have no like, pros to learning one over the other, let’s say like your your job doesn’t have one they’re using, I would I would personally recommend Vue.
Yeah, I think that I agree with the learning curve aspect of that that Vue is a little bit less of a steep learning curve. So I think another thing with React that we didn’t talk about is that it is highly based on the functional programming paradigm. So there’s a lot of like immutability where you don’t change existing data structures and a lot of other complications that come along with that. Where Vue does not have that. Like there’s two-directional data flow, whereas in React the data structures or the data flow is unidirectional. So you pass data from one component to another, but you don’t pass it back to that original component. Whereas [in] Vue the components can really talk to each other. I think that that data flow makes learning Vue a lot more accessible. That being said, my one thing for React is that, especially in the States, I see a lot more React jobs than Vue jobs. And so if you’re looking for your first developer job, I would recommend learning React for that reason.
I agree. That’s awesome. So speaking of really great frameworks, I’m going to now segue into one that I’m not passionate about. And I hate that I say that because I think I just had a bad experience with it. I am going to be neutral on this topic, but that’s Angular. Angular’s… Okay, well, let’s be clear here. We’ve got AngularJS, and we’ve got Angular, and they’re technically two different frameworks, which is very confusing to me. But let’s talk about that. So AngularJS was released in 2010 by Google. Again, similar to React, it was backed by a large company. It’s currently being used by many big companies like Forbes, Wix, and you guessed it, Google. So today, it’s called Angular. But prior to 2016, there was the suffix JS. They’re not the same framework. And this is very confusing to me. It seems as though every new release of this framework kind of changes the paradigm vastly. And so, like, the AngularJS release is not even remotely the same framework as Angular, although I don’t know Angular at all. So like, I’m not one to speak to those. But from what I can tell, there are some pros. It seems like it’s pretty modular. They had… there’s a lot of out of the box functionality that you get like a router, form validation, a HTTP client. You have a high level of control. And you can also just apparently, use HTML and CSS, you know, natively versus React. We talked briefly about JSX. And that being a little bit different. But again, Angular, lots of different releases. A little tricky to learn and each version differs vastly from previous versions.
Yeah, I think there are huge benefits to using React or Vue even just for a side project for developer friendliness, whereas Angular is not that way. Angular really comes in if you’re building a massive enterprise application and need all the bells and whistles and need it to be really, really structured. I think that’s where Angular really shines, whereas React and Vue still shine for smaller projects as well. So we both used AngularJS back in the day, and it was really painful to debug and work with, at least in my opinion, and then Angular, when it was released, it mirrored React in a lot more ways. So it used this like component-based architecture and all that that we’re seeing with the other frameworks. And so that change is when it dropped the JS from its name and is now just Angular, but they change versions really fast. And they even have Material Design built into it now. So…
Emma 41:55 Oh, wow. Okay.
Ali 41:56 It has everything coming out of the box, you don’t even have to install really anything to, to Angular. So it’s definitely really interesting from a lot of perspectives. And it was the OG in a lot of ways. But I personally have a lot less fun writing Angular code and teaching it is really, really tough. Whereas React and Vue are…
I would argue, though, that you can definitely build large scale enterprise applications with React if you use some of the other tooling that comes along with that, right. Like if you’re, we’re using React Redux here with TypeScript. And I don’t know, I don’t think we’re using GraphQL but that also plays nicely with it. Yeah, I would agree that maybe Angular is a bit more robust out of the box for enterprise apps, like there are things that you can do with React that also level that playing field.
Oh, a hundred percent. I 100% think React is excellent for massive applications. For sure. I’m more saying that Angular does not work well with small applications, but apparently it works well with bigger ones. And so I haven’t had as many experiences that make Angular necessary. Whereas I’ve heard from people who work for like massive companies that Angular is better enough. Or Angular shines in that format. Not that it’s like better than anything else in that format, but that it’s not good or not great in a very small application, if that makes sense.
Yeah, I think it goes without saying that any of these frameworks have their place that you know, they really shine, depending on what it is your end goal is. And while we may not have maybe positive opinions of Angular or have not had the experience to really sit down and learn it in a real life context. I know a lot of people absolutely love Angular. And that is definitely their framework of choice. So if it is something you’re interested in learning, there’s definitely plenty of. There are resources out there for you to learn.
Totally, totally. And their documentation is really good too now.
So we’ve kind of talked about, you know, three of the biggest frameworks or libraries, React, Vue and Angular. There are definitely some others that you you can check out and that are, you know, still pretty popular. So like you might have heard of Ember, Backbone… Svelte? I think that’s how you say it, right?
That’s how you say it. Yeah, I had to learn that one too.
Sveltee? Elm and Hyper. I mean, there are numerous… many frameworks. I mentioned Dojo. I was using, like Durandal with Knockout… Like there’s a plethora, right? How do you know which one is right for you?
So I think if you’re working at a big company, I think the biggest question is, what are you using already? And is that working for you, if it’s working for you, there’s no need to change it. And you don’t need to have shiny object syndrome and change to the hottest framework that’s out there right now. If it’s working for you stick with it because your developers are already onboarded to that, that’s perfectly valid. That being said, if you are in a situation where your company isn’t using anything yet or you are starting from zero, my personal spin would be that like React has a huge ecosystem behind that at this point, Vue does as well. And so then it comes down to what your developers know, what level they’re at, like junior developers… We talked about how Vue is easier to learn, usually. And so if your team is all juniors, like, maybe Vue would be the way to go. But then React has been around longer, is a little bit more popular. So maybe it’d be easier to find React developers to work on your projects. So that’s really important to think about all those different pieces of the puzzle there.
Absolutely. I think that’s great. Yeah, I think that’s it. That’s a mic drop right there. I don’t have anything to add.
I think we just… we over dramatize everything.
Ali 46:33 Yeah. That’s true.
But I also feel like maybe in the past that that was true, and people had the right to be kind of upset, not upset, but like nervous about that, because the amount of educational material took a lot longer to be released, when new iterations were produced of these frameworks, right? But now we’re in an era where there’s so many people producing content, amazing content, that you know, something gets released. Like hooks got released and like all these big people started pushing out content like the same day or a few days after. So I think back in the day, I could understand that. Now I think we’re in a different time.
Yeah, totally agree with that. I think that it’s really stabilized in a lot of ways. There’s a great ecosystem, in like 2015 2016 I think that was super true with Gulp and Grunt and Webpack and Parcel and all of those things moving and not knowing which framework would actually become dominant. But now I think that it’s really stabilized in a lot of ways.
Agreed. So let’s talk about learning one of these frameworks. And I know that each of us have some of our favorite tutorials for learning various libraries and frameworks. So Emma, what are some of your favorites?
So in terms of React, I… even today, I’ve just been taking Tyler McGinnis’ React tutorials, because he’s an incredible teacher. He teaches things I would not even think that I needed to know and he reinforces that information in a way that like, you watch a video and then you read an associated blog post, and then you do activities. And so having like different methods for learning really helps you absorb that information, so shout out to him and then also Dave Ceddia has a Pure React book I would highly recommend as well. What about you Ali?
Awesome. So my go-to is going to be the documentation. I like reading stuff and just trying to use those primary sources first, and I think React and Vue both have really great documentation on their site. Angular does too at this point, as well. I also wrote my own React and Vue tutorials, so you can read those. Some people like them, so hopefully they’re helpful. So, I don’t know, I guess I’m doing a shameless self promotion here but those are out there.
Some people like them? Give yourself some credit. People love them. They’re great tutorials.
Ali 48:50 Kelly, how about you?
Kelly 48:51 So one of my favorite courses for learning Vue was Sarah drabness course on Frontend Masters. That was kind of my first foray into Vue before I jumped into working on this client project. And I found it to be incredibly helpful. And when I started learning React, I use the React for Beginners tutorial from Wes Bos. I thought that was a really great intro. And I thought the… like the activities that you do as you’re learning, as you’re going through the tutorial, were fun. So it kept me engaged as well. So those would be my two favorites.
Emma 49:26 I want to thumbs up both of those because I took Sarah’s Vue course on Frontend Masters and, I mean it was only a couple hours, but I was able to build like an enterprise website based on that. So that was really great. And I would also thumbs up Wes Bos has some really fun activities.
Kelly 49:38 I think a lot of Wes Bos’ tutorials are really great. Just the various courses.
Emma 49:42 Right.
You can also take those and then use… like build the same thing but using React or build the same thing using Vue. It’s really interesting.
It’s totally. There’s this site that’s called TodoMVC. And it does this for both frontend and backend frameworks. But it builds the same To Do List app in like every single framework you can imagine. So you can see the different code for each one. I think that that’s a really great resource too. So I thought this episode was really educational for me, as well as hopefully the audience. So if you liked this episode, tweet about it. We select one tweeter each week to win Ladybug stickers. They’re super cute. And if you know somebody who should be a guest on our podcast, visit our contact page on ladybug.dev to submit a name. On that site we also have our transcripts and full show notes. So definitely check it out. We post new podcasts every Monday, so make sure to subscribe to be notified and leave a review. We love seeing your thoughts. Thanks again to LogRocket for sponsoring this episode.