Video details

My Response To Fireship

Career
03.05.2022
English

Need help with you career? Looking to get into big tech? Let me help you! One week free trial! 👉https://mentorcruise.com/mentor/erikhanchett/
Can you learn Vue in 100 seconds? In this video I respond to Firebases learn Vue in 100 seconds and give my opinion on it!
👉Check out Vue JavaScript Survey https://youtu.be/UmkEDc1G_7A
👉 Sign up and get free Vue cheat sheets and updates! https://www.vuecourse.tech/
Need some mentoring, help with a project, get a career in tech, level up your skills? Check it out 👉https://mentorcruise.com/mentor/erikhanchett/
Need to Learn Vue or Nuxt? Check out my courses below!
http://bit.ly/2LalQka - Learn Nuxt.js Course! http://bit.ly/3aiYe8s - Quick Starter On Vue 3 https://bit.ly/2OETt0M - Full 6 Module course on vue!
0:00 Introduction 0:30 React to the video
Links https://youtu.be/nhBVL41-_Cw

Transcript

Hey developers. So today I was clicking around YouTube and I saw a video titled View JS explained in 100 seconds by Fire Ship. So I thought maybe I would go and take a look at this and see what other people think about View. And can you teach Vue in about 100 seconds? And me being the self proclaimed King of View on YouTube, I thought this would be a fun experiment to see what you guys think. Hey, and if you like this type of video, make sure you smash that like button. Yeah, let's just jump into it. Bjs it's a JavaScript framework for building front end UIs in View. You can start simple and then progressively add in the tools and features that you need to build a complex web application. Yeah, exactly. That's what it is. It's called the progressive framework. So I already like how this video is starting off with going over what it is. So let's keep going. At its core, it provides a way to build components that encapsulate data or state in your JavaScript and then connect that state reactively to a template. In HTML, we call these components declarative Views because the same data inputs will always produce the same output in the visual UI. When we declare data on this data object, it links or binds it to the HTML. On the template above, when the value of the data changes, the component will automatically rerender. Or in other words, it's reactive. Yes, he's absolutely right. This is actually the Options API, so it's a little bit out of dated. A lot of View developers still use the Options API, but we do have something called the Composition API, but the basics are the same. We have this reactive data that you can change between the script, it updates the template, it's bound, and it's reactive in that way, much like React and other frameworks. And the framework does a ton of work under the hood to make sure that this process is performance across a huge component tree. We can work with this data in the template thanks to Views HTML based template syntax. We can interpolate and sometimes call like the mustache syntax. But yes, that's how we do it with the double curly brackets. It's good to know too, if you're learning preview for the first time. This is the way you should probably learn View. However, you can opt out of this and use JSX. In fact, if you use VT, maybe even asks you in the latest UI tools for View, it asks you if you want to install JSX. I do like this because it makes things very simple for people learning View a value or expression using double braces. And we also have a variety of directives to control the behavior of the HTML based on the data. We can use vif to only render an element when the value on the right side is Truthy, and then we might have a fallback element after that, that's only rendered when the value is Falsey. With VLS, we can make the app interactive by listening to events. It's worth noting too, that you do have the if you have VLS, you have VL. If you also have some other directives that make things easier. There's the show. There's a whole bunch of different directives that you can use that make your life easier in the View world. Using the V one directive, we can listen to an event on an element, then run some code to handle that event on the right side. We can do that directly in the template or define a custom method in the Components methods object. The method has access to our reactive data, and that means all we have to do is change the value of the data and the component will automatically rerender. I like how simply puts that. It's definitely that easy with that Von directive. My face may have been blocking it, but there's the at which you can use as a shorthand instead of typing in the on all the time. He also didn't mention other things like computer properties, which I find really helpful and useful. Usually it's a way to cache different values. Either any of those values and your computer property change it recalculates. It's a little bit more powerful than using methods. So far. I'm impressed by this 102nd video. An interactive, reactive declarative UI component with you. The framework is loved by developers for this simplicity, but also its ability to scale up in complexity. Incrementally. Its plugin system allows you to easily drop in things like a router, state management, Firebase support, and more. Yes, you can definitely use this plug in system. It's really similar in View Two and View Three. You can just add these in here. You're using V Two. There's a whole plugin system within VAT as well, but that's more of the tooling behind it. It's not View specific, but that's usually how a lot of new View developers are creating new apps is on Lead as well. Also, in the View CLI world, there's a whole plug in system inside there too. If you're interested in looking into that. I did a whole video on how to create a View plugin. If you're interested, I'll put a link up here. And perhaps best of all, it's not sponsored by some megacorporation. It's not pressured to push out new releases all the time and does a great job listening to its community. This has been v. Js in 100 seconds. One note on that. Yeah, definitely. Unlike Facebook that has React or Angular that has Google, View is its own platform, its own framework. It's not backed by any big corporate entity. I will say though, that it's really cool. Since everything is open source, you can support the community creators, which I'd highly recommend. You can go to the GitHub repo. There's a whole bunch of core members and a lot of them have ways you can donate money to them and also Evanu, it's his full time job to work on view and vet and his other projects and he gets that by his own Patreon but he also has sponsorships so if you put a sponsorship on the View homepage he gets some of that. It's a really cool ecosystem that they created here that we have developers that actually get paid to work on view and to make it better. Yes, I would say overall I'm really impressed by this video. In 100 seconds he definitely hit the high points of view. The simplicity of it, the reactivity of it, how to use directives. It would be nice if it would have been like three or four minutes or longer. He could have gone into computer properties, the new composition API the script set up API actually is a lot different and I think that's where the View ecosystem is moving and I wish he would have covered that but maybe during the time this video was created maybe that wasn't really a thing. Yeah, I like this video. I check it out. I'll make sure there's a link to it in the bottom in the description. If you guys like me doing these to react to these type of videos, let me know and I'll do a few more of them. Thanks.