Video details

WWCode San Diego Lightning Talks: Angular for Enterprise by Julie Knowles

Angular
12.14.2021
English

Presented by Women Who Code San Diego Speaker: Julie Knowles Topic: Angular for Enterprise: 10 Reasons in 10 Minutes (or less)!
___ 💻 WWCode Digital Events: https://www.womenwhocode.com/events 🔎 Job Board: https://www.womenwhocode.com/jobs​​​​ 💌 Make a Donation: https://www.womenwhocode.com/donate

Transcript

Okay, here we go. So my name is Julie Moles. I am the Angular lead for women who code along with Mechi. And today I just want to give you a brief introduction into why you might want to use Angular for enterprise. I'm speaking big companies. I work for Teradata, and we're a large company and just want to get into why you might want to consider this instead of another framework. The first one is maintainable code. Angular is written with TypeScript, and I personally like TypeScript. I like the typing. It reminds me of olden days, and you used to have to type in other languages, and it helps keep developers on the same page because it promotes a little bit of standardization. You're all writing in the TypeScript, it's heavily. If you're linting it and using prettier, then you're able to control all the code and looks rather similar. And so I think that's a good benefit for using Angular for enterprise applications. It's a component based architecture, and components are the foundational blocks of Angular, and they are cohesive and self can't think of the word they're all contained in their own little world, so they're reusable maintainable and easy to test because they're in their own world. That's not the right word, but the commandline interface. Angular has got a really nice command line interface that makes it easy to create everything that you need for your application, whether it's components, guards and services, or there's many other things you can do with the command line interface. It simplifies the whole development process by automating processes such as app initialization and configuration, and you can add features and new components and things to your enterprise application in minutes by using the CLI. And you can also use it to run tests on individual component or the entire suite with a few simple commands. The fourth is dependency injection, which has been a feature of Angular since Angular JS days, and now it has improved hierarchical dependency injection, so it decouples the components from their dependencies by running them in parallel to each other. The classes themselves don't have dependencies, but they consume them from external sources. So again, for the components are all compartmentalized in their own way and makes it a lot easier to just again share and reuse. And you can easily test because the dependencies themselves can be mocked. Angular also has server side rendering with Ivy, which is their newest generation of Angular compiler. And the Angular compiler translates the components of your app into a language that the browsers can display. And one of the biggest features of IV is the tree shaking technique. So it eliminates code that you're not using, which results in an application which is lighter and loads faster and breaks it up into smaller chunks as well, which is helpful for the large enterprise apps. The 6th reason is Angular universal. We don't personally use Angular universal. I never have, but my understanding is that it allows applications to be rendered on the server instead of the client browser, and this helps with increasing the traffic to your web app, facilitating higher search engine rankings, reducing the load time, and improving mobile performance. The 7th is not actually a part of Angular, but NX by Narwhal is an open source toolkit for Angular enterprise applications. You're not really going to want to use this for a small application, but it is great for enterprise applications. It creates a mono repo, which is good for enterprise large companies that have multiple groups working on the same code base. You can keep everything separate. Each app can be its own piece in the mono repo, but you can all use the same Dev workflow to create your applications and then tie them all together. Since you're doing this, we're back to the code is easier to reuse and integrate since teams are on the same page. It also provides its own set of tools, which are very helpful as well. The 8th is Angular Design and Angular Material. Angular was originally created by Google, and Google has their Material Design, which is the backbone of Angular Design, which Angular Material builds on. So Angular Material is a library of UI components and behaviors for creating UI components, and so you can make your app look consistent across the board, no matter who's writing it, by using these UI components and the different options for that. Licensing concerns. I actually didn't realize this until I was just looking into this, but React has a patent clause that can make it difficult for companies that want to patent their products that use React. Because Angular is entirely open source and there's no concerns about with licensing or patenting you might want to use, you might want to consider that. And then finally, the community. The community itself is such a huge and helpful group. There's podcasts of which Miji has given to. There's a lot of meetups in most major cities. And again, Michael and I run the Angular meetup here in San Diego for Wednesday of every month. And there's two large conferences, usually the Ng conference, which is in April or May, and the Enterprise Ng was just last week. But anyway, this is just touching a little bit on why you might want to look at Angular for your front end if you're an enterprise company. Thank you, Julie. I love how there are ten reasons. What was that? I love how it's ten reasons I didn't know or less. Yeah, it was just what I came up with. Does anyone have any questions? You can take one or two. Feel free to unmute or write and chat. How does Angular update? How does Angular update? Yes. Isn't there like a big breaking change from Angular one to two? And now they're always going to break stuff on you. Me too. Are you giving me a hard time? Anyone who's used Angular in the past will remember the days when there was Angular, JS, and now there's Angular. So, yes, there was apparently actually Narwhal or the NX. I think it was NX or one of them can help with updating if you're using AngularJS. But yeah, there were a lot of breaking changes between one, which is called AngularJS, and two moving forward, which is Angular. But it's not an issue now. Michi, good to know. I had no idea before. Oh, yeah, sure you didn't. It's just another reason to use Angular for enterprise apps because it's not an issue now. Yeah, exactly. You're right. It's not an issue now. And they've been wrong around for longer, genuinely like that's. The biggest reason people say to not use Angular is because they break and they dump those. Not anymore. It was a little troublesome back then, but not anymore. There's a wonderful thing called Ng update. I want to say it's like React is still in its sub zero when Angler Two came out. Yeah. And they were breaking all the time. That's still my biggest complaint for React. And they don't do that anymore. But I still complain about it. Right. I do have a little sympathy for the people who are like, AngularJS broke once and never again. Yeah. Julie, did you attend Enterprise Ng? Yes, I did. Well, I got to listen to the first keynote, and then I got wrapped up in work, but I am going to go back and watch this stuff. But I did wash the keynote. Was the keynote good? It was quick. It wasn't the best keynote I've ever watched. They kind of just ran through a whole bunch of stuff really quickly and it turns wow. Okay, well, that doesn't matter. But one of their main guys is leaving. So what I'm hearing is Angler's going to break. No, Leslie. No, not anymore. Not anymore. Awesome. Thank you so much, Julie. Yeah, that was super informative. And I think Kat also had a comment about not knowing about the patenting. Yeah, I can't say that word. Patenting. Patenting. That was really cool to learn, too. And actually, from what I read, it's still an issue because I was thinking because what I originally saw was back in 2017. I thought, well, maybe it's not a problem anymore. But I found a recent article just this year that makes it sound like it still is a possibility. That's really interesting because a lot of companies use React and build their IP on React. Let me see if I can find because there was an article. Maybe I'm wrong. Can I cut and paste this? Give me 1 second. I'll see if I can. While we move on, I will cut and paste the link into the chat and you can take a look to see. Sounds good. Thanks for sharing. Sure. Thank you for the presentation. Sure. Next we have Leslie. Hello, folks. I didn't know what to do my talk on, but this has been what I've been researching endlessly. I've been around the web since the 90s. I've been part of 1.02 .03 .0 I am still not an internet millionaire and this is why I've been researching this because I'm like can I become an internet millionaire? Dao seems to be the buzzword of the last few months. So we're going to go over what it is. Is it a scam? If you folks need to go take a bathroom break or something, probably it's a scam, but we're going to go through why I think maybe it's not for me. It might be for you though. Bye.