DiscoverThe Angular Show
The Angular Show
Claim Ownership

The Angular Show

Author: ng-conf

Subscribed: 45Played: 1,384
Share

Description

The Angular Show is the home of ng-conf's official all-Angular podcast. Come here to stay up to date on the latest changes in the Angular community. Expect to laugh and cry with us as we talk about our experiences as Angular developers.
54 Episodes
Reverse
E053 - RavenDB

E053 - RavenDB

2021-04-0601:11:58

We here at the Angular Show strive to deliver fun, newsworthy, and exciting developments in the Angular community. And, while databases may not be something you are familiar with or really have to even worry about, we wanted to take a break from our usual programming to reflect briefly on data persistence. After all, you need to put your user data somewhere, and we don't recommend stuffing everything into localStorage.In this episode, panelists Brian Love, Jennifer Wadella, and Aaron Frost welcome Oren Eini, founder of RavenDB, to the Angular Show. Oren teaches us about some of the key decisions around structured vs unstructured databases (or SQL vs NoSQL in hipster developer parlance). With the boom of document-driven unstructured databases, we wanted to learn why you might choose this technology, the pitfalls and benefits, and what are the options out there. Of course, Oren has a bit of a bias for RavenDB, so we'll learn what RavenDB is all about and why it might be a good solution for your Angular application.Show Noteshttp://howfuckedismydatabase.com/nosql/Shadon: https://www.shodan.io/Data Breaches: https://www.informationisbeautiful.net/visualizations/worlds-biggest-data-breaches-hacks/Israel COVID Stats: https://datadashboard.health.gov.il/COVID-19/generalConnect with us:Brian F Love - @brian_loveAaron Frost - @aaronfrostJennifer Wadella - @likeOMGitsFEDAYOren Eini - @ayende
In the final part of our series on RxJS operators we welcome Zack DeRose, senior engineer at Nrwl, back to the show to learn about multicasting, error handling and utility operators. To kick things off we do a quick recap of hot vs cold Observables, unicast vs multicast, and then the Subject class as well as a few of its child-classes.You might be wondering, "What is a multicasted Observable; Why would I want that; and what is the implication for my application?" In short, the multicast operators provide the functionality to create a multicasted Observable (duh! and huh?). The complexity and confusion usually arise around what operators to choose from. Why would I choose publish() over shareReplay()? And, what about ref counting? Don't worry - panelists Aaron Frost, Brian Love, and Jennifer Wadella, along with our esteemed guest Zack, answer these very questions.We then go into detail on error handling in RxJS and the various operators for error handling, from catchError() to throwError(), and everything in between. Finally, we talk through various utility operators such as tap() and delay().While you don't need to have listened to the first 3 episodes on RxJS operators in this series to enjoy this episode, we do recommend you check them out if you haven't already. Be sure to subscribe so you don't miss a single episode of the Angular Show!Show Notes:WTF is a cold observable: https://www.youtube.com/watch?v=4btjdWHM6lI&ab_channel=AngularSeattleDeRose Hpothesis on Code Complexity: https://www.youtube.com/watch?v=H9EZZDREMEk&t=779s&ab_channel=AngularSeattlezackderose.devMulticasting: https://dev.to/bitovi/understanding-multicasting-observables-in-angular-2371Connect with us:Brian F Love - @brian_loveAaron Frost - @aaronfrostJennifer Wadella - @likeOMGitsFEDAYZack DeRose - @zackderose
E051 - Indigo Design

E051 - Indigo Design

2021-03-1001:17:31

The Angular Show welcomes back our friends from Infragistics to talk about their new App Builder prototype as a low-code solution to building Angular applications that integrate seamlessly with their Indigo Design platform. Infragistics is a design and development company that also builds tooling and products to enable developers to build robust applications in .NET and Angular. In this show, we welcome George Abraham and Konstantin Dinev back to the show to teach us about design systems and their low-code solution for Angular.We start out by learning about design systems and the importance of using a design system to integrate the UI/UX team with the development workflow. In many organizations, there is a gap between these two teams, and further, making feature iterations and scaling designs across many applications can be difficult and complex. Design systems seek to solve these issues. Infragistics Indigo Design is built with this purpose in mind.Infragistics' new App Builder build (see what we did there) on Indigo Design to provide a low-code solution for application prototyping and development. Imagine taking your UI design, building the design and navigation using their cloud solution, and then downloading the resulting Angular application that is ready to go. Now now, you might find this a bit scary being an Angular developer. But, have no fear, the panelists ask the tough questions for you, such as what about the quality, maintainability, and testability of the generated code?? We think you'll be pleasantly surprised to learn what the team at Infragistics is building. Besides, who really enjoys spending hours writing out semantic HTML and CSS?Head over to infragistics.com to learn more about Indigo Design and the new App Builder for Angular. Check it out, and let us know what you think!Show Notes:Indigo Design: https://www.infragistics.com/products/indigo-designApp Builder: https://www.infragistics.com/products/indigo-design/app-builderIndigo Design Feedback: feedback@indigo.designConnect with us:Brian F Love - @brian_loveAaron Frost - @aaronfrostKonstantin Dinev - @KonstantinDinevGeorge Abraham - @jabberSGA
In the final installment of our series on forms, the Angular Show welcomes one of our favorite speakers and expert on forms, our very own panelist, Jennifer Wadella. Jennifer is the Director of Angular Development at Bitovi, a front-end JavaScript consulting firm.In the first two installments, we discussed Angular Formly with Bram (better known as Beeman) and Juri Strumpflohner, and then we sat down with Ward Bell to expand our understanding and appreciation for template-driven forms. In this episode, Jennifer will take your knowledge of reactive-driven forms to the next level. To get started, we will broadly discuss the basics of reactive forms and its API; including the AbstractControl, the FormBuilder, and more. We'll then briefly learn about the differences between using the reactive forms API and the template-driven approach. We'll also discuss some more advanced topics, such as the value control accessor and validation. Finally, we'll look at a few of the open issues related to reactive forms and discuss how the API could be improved (ehh hemm, typings).If you haven't subscribed to our show, go ahead and do it now. We love this community and we want you to be a part of it! The Angular Show is your home for the latest Angular news, to learn more about Angular, and to meet amazing people in the community.Show Notes: ngx-typed-forms: https://github.com/Quramy/ngx-typed-formsStrong typings: https://github.com/angular/angular/issues/13721Andrew’s reply: https://github.com/angular/angular/pull/40772#issuecomment-776456955 Improvements: https://github.com/angular/angular/issues/31963Control touch state observable: https://github.com/angular/angular/issues/10887Control.getValidators() is missing: https://github.com/angular/angular/issues/13461Input as Observable: https://github.com/angular/angular/issues/5689Identity made simple for developers with Auth0 - https://a0.to/youtubeDemo: How to add user login to an Angular application using Auth0 - https://a0.to/angularSDKqsConnect with us:Brian Love - @brian_loveJennifer Wadella - @likeOMGitsFEDAYAaron Frost - @aaronfrost
In part 3 of our series on RxJS operators, the Angular Show panelists Aaron Frost, Jennifer Wadella, and Brian Love, along with our friend Lara Newsom, take a stroll through the filtering operators. The filtering operators enable developers to filter next notifications from an Observable.The most logical filtering operator to start with is, well, you guessed it, the filter() operator. From there, we look to the operators that only emit a single next notification: first(), last(), find(), and single(). Most of these operators are fairly straight-forward, and often have an optional predicate that can be provided to determine when the operator returns a new Observable that immediately emits the next notification to the Observer, or to the next operator in the pipe. Moving onward Lara teaches us about the family of take() and skip() operators. We didn't list them out here since we are lazy and don't want to type them all out, plus, you should really just have a listen to the show and subscribe! Ok, phew, now Lara and the panelists talk about the ignoreElement() operator, which like the window() operator, has nothing to do with the DOM. Rounding the final bend in our run through the filtering operators we talk about the family of distinct() operators. And, with a sprint to the finish line, we learn about the audit(), debounce() and simple() operators for rate limiting. Speaking of rate-limiting, this is getting long. But, thankfully, this show on the filtering operators is not that long, plus, you can always expect a good time hanging out with the Angular Show. Enjoy!Show Notes: https://dev.to/rxjs/debounce-vs-throttle-vs-audit-vs-sample-difference-you-should-know-1f21Connect with us:Lara Newsom - @LaraNerdsomBrian Love - @brian_loveJennifer Wadella - @likeOMGitsFEDAYAaron Frost - @aaronfrost
What is a linter? For some, a linter is that round brush-thingy with sticky paper that you use to remove your cat's fur from your otherwise beautiful jacket before going out in public. For computer software engineers, a linter is a program that uses static analysis to determine if there are potential errors, stylistic problems, or other suspicious operations in an application. Attempting to use your lint brush with an Angular application might be tricky, or perhaps, it's an alternative method to cleaning the grime off your screen that has been there for months and you can somehow see past every day. Instead, Angular developers have long relied on tslint, which is a lint tool specifically built for TypeScript. Things were good, well, mostly good, up until last year when, in the midst of quarantining and eating ramen, you read a tweet that said maintenance of tslint was coming to an end. So, what is an Angular developer to do?Enter James Henry. James is a Consultant Architect for Nrwl, and generally coined by the Angular Show, as "that good looking guy at Narwhal" (not that everyone else isn't beautiful). James has worked alongside the eslint team for many years, and has provided a solution to those using TypeScript, and thus tslint, to migrate and leverage the power of eslint. James talks through his journey working with eslint, TypeScript, and more. To further prove that James good looking (scratch that)... an outstanding contributor to the community, James has provided a migration path for the most common tslint rules to eslint rules.Should you migrate to eslint today? How difficult is it? What about my existing tslint rules? Those are all great questions, and the panelists will explore and learn from James the answers to those questions and more. Go ahead, subscribe, and have a listen.Show Notes:discord.gg/angularhttps://astexplorer.net/https://github.com/typescript-eslint/tslint-to-eslint-confighttps://github.com/angular-eslint/angular-eslinthttps://twitter.com/cotufa82/status/1355901060636930049Connect with us:James Henry @mrjameshenryJennifer Wadella @likeOMGitsFEDAYBrian Love @brian_loveAaron Frost @aaronfrost
Angular is a feature-rich and opinionated framework. Opinionated, for example, in terms of fetching data via XHR. Most, and perhaps all, Angular developers reach for the HttpClientModule. Most of us don't have to even think about that decision. While the debate will likely never end over JavaScript frameworks, Angular developers may never end their debate over what forms implementation to use. Do you use reactive forms (which are arguably not really reactive) or template-driven forms? The Angular show panelists want to take you on a learning journey into the depths of this debate in a healthy, fun, and educational way.If you read the Angular documentation you might be inclined to believe that Angular's template-driven forms approach is where you start, but real Angular devs use reactive forms. I mean, the name reactive is hip. And template-driven forms, that's so AngularJS-y. Why would I want to use template-driven forms?We have the perfect guest to answer that question for you. Ward Bell, a Google Developer Expert in Angular and President/Co-Founder at IdeaBlade, has put template-driven forms through its paces for many years, and in our opinion, is one of the foremost experts on using template-driven forms in Angular. Grab your kombucha, coffee, running shoes, or really whatever you want, and join us as we learn from the master on template-driven forms. By the end of the show, you might be asking yourself why you aren't already using template-driven forms in your Angular applications.Bonus notes from Ward after the show:I talked through a couple of approaches during the show but I didn’t have an actual sample to refer to... I just updated the StackBlitz sample with an example of both approaches. Color me “obsessive”.https://stackblitz.com/edit/angular-kkatri?file=src%2Fapp%2Fhero-form%2Fhero-form.component.htmlThe hero now has both a “Power” and a “Power Qualifier” (category and subcategory). Both are required. You pick a power and the list of qualifiers changes accordingly. A special “Select a power qualifier” appears until you pick a qualifier. This demonstrates the “disabled control” approach.One of the selectable powers is “Other”. It has no pre-defined qualifiers. Instead, you must enter a free-form description of the “other power”; what you enter is bound to the hero’s qualifier field.When you pick “Other”, the “Power Qualifier” selector is removed from the form and a required free-form input control takes its place. This is the alternative “ngIf” approach that I mentioned.Click the “New” button to see how it works when Hero has no power.Show NotesAbstractControl: https://angular.io/api/forms/AbstractControlConnect with us:Aaron Frost - @aaronfrostJennifer Wadella - @likeOMGitsFEDAYBrian Love - @brian_loveWard Bell - @wardbell
Developing on the web can potentially be reduced to inputs and outputs, and further, a snapshot of current inputs and outputs is the state of our application. Inputs often come in the form of user events, and one of the primary methods for users to provide input into our applications is through forms. Whether you love or hate forms, web developers have no way of escaping this critical input method. In this episode of the Angular Show, our panelists are joined by two experts in the area of Angular and forms, Juri Strumpflohner and Bram Borggreve. Juri Strumpflohner is a Senior Software Engineer at Narwhal and Bram is a freelance developer and founder of BeeSoftLabs. Juri and Bram are members of the Angular Formly core team that produces and maintains this open-source project. While Angular ships with powerful form modules, Angular Formly builds on top of Angular's modules to provide an abstraction layer that enables developers to build robust and complex forms. One of the biggest advantages is the ability to dynamically and programmatically define form groups, arrays, and controls. Further, Angular Formly provides wrappers for control appearances based on several popular UI component libraries, such as Angular Material and Bootstrap, or you can create your own UI wrapper if necessary.Connect with us: Juri Strumpflohner - @juristrBram Borggreve - @beeman_nlAaron Frost - @aaronfrostJennifer Wadella - @likeOMGitsFEDAYBrian Love - @brian_love
Micro-what?!? What is a micro frontend, what does it have to do with Angular, why would I want to use this strategy, and how do I go about implementing this in my organization?These are all good questions. Whether you know what a micro frontend is, have never heard of it, or are currently implementing this strategy in your organization, this is an episode of the Angular Show that you do not want to miss.Join panelists Aaron Frost, Brian Love, and Jennifer Wadella as they start their journey in learning about Micro Frontends in Angular. We had the privilege to sit down with Zama Khan Mohamed, who is an expert in Micro Frontends. Zama teaches us the basics of what a micro frontend is and why we would consider this strategy for our applications. Then, we dive into the details on how Angular developers and organizations using Angular, as well as a mix of other frameworks, can leverage Micro Frontends in their architecture. We also discuss some of the benefits and costs of this approach, and why you might want to consider using micro frontends. Finally, we also touch on Webpach version 5's new support for federated modules and the impact this has on how we build modern micro frontends.Phew - that sounds like a lot, but have no fear, your friendly panelists are here to walk with you through this new landscape of micro frontends in the JavaScript ecosystem.Show Notes:https://github.com/single-spa/single-spahttps://webpack.js.org/concepts/module-federation/Connect with us:@mohamedzamakhan@likeOMGitsFEDAY@brian_love@aaronfrost
Securing your Angular application is almost always necessary. And, it's almost always unnecessary for you to roll your own solution to authentication and security. Why? First, security is not easy and straight-forward. At first, you might be tempted to think, "Well, it's just a form with two fields, email, and a password, right?" Not really. Securing your app is complex, constantly evolving, and is critical to your application. Finally, implementing your own OAuth-based social account authentication can be mundane, and perhaps even trivial. You, your team, and your organization should prioritize what you know and do best: building your app.While there are many identity providers to choose from, Angular Show panelists Jeniffer Wadella and Brian Love wanted to learn more about the solution provided by Microsoft. So, we sat down with Christos Matskas from the Microsoft Identity Product Group to learn more.Microsoft Azure provides a robust infrastructure and tooling for securing Angular applications. And getting started only requires an Azure account and your existing knowledge of Angular. First, you register your Angular application, then you can configure your Angular application using the Microsoft Authentication Library for JavaScript. The Microsoft Identity Product Group team has also built a wrapper on top of the JS library specifically for Angular, making it very easy to install and import the necessary module into your Angular application's root module to configure your application. The team also provides plenty of source code examples in their documentation specific to Angular. Using Microsoft Identity platform, you can rest assured that your application is secure, and the security of your application is following best practices from security experts.Join us as we learn about the benefits of using an identity provider, the specific implementation of using Microsoft Azure identity solution with Angular, and how you can get started. Don't forget to subscribe to get more great content from the Angular Show!Show Notes:https://medium.com/identity-beyond-borders/what-the-heck-is-pkce-40662e801a76https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-v2-angularConnect With Us:Christos Matskas - @ChristosMatskas@AzureAndChillaka.ms/425Showaka.ms/425Show/ytaka.ms/425Show/blogaka.ms/425Show/discord/joinJennifer Wadella - @likeOMGitsFEDAYBrian Love -@brian_love
Join us in part two of our series on RxJS Operators. As Angular developers, we rely on RxJS primary for asynchronous operations via the Observable primitive. While we can think of an Observable like a Promise, and simply subscribe, we can also take advantage of the many, many operators at our disposal for the transformation of events and data within the Observable stream.In order to learn more about RxJS transformation operators, we invited Lara Newsom and Zack De Rose to the podcast. Lara and Zack have a wealth of knowledge in both Angular and RxJS. Lara is a software engineer at Source Allies, a technical consultancy located in Iowa; and Zack is a senior software engineer at Narwhal, where they build Nx and Nx Cloud, as well as provide Angular consulting services.To get started, the group tackles the mapping operators, including map, pluck, scan, and reduce. They then dive into the various higher-order mapping operators, including switchMap, exhaustMap, mergeMap, and concatMap. Learning the different behaviors of each of the mapping operators is important when determining which operator to use within the pipe method. Next, the panel talks about the buffer operators, including buffer, bufferCount, and bufferTime. This then leads into discussion about the window operators, including window, windowCount, and windowTime, all of which have nothing to do with the global window variable in JavaScript when executing in the context of a browser.This episode is jam-packed with great content, humor, and fun. Don't forget to subscribe so you can continue to join us in our journey of learning about RxJS Operators.Lara Newson @LaraNerdsomZack DeRose @zackderoseAaron Frost @aaronfrostJennifer Wadella @likeOMGitsFEDAYBrian Love @brian_love
The Angular Show is primarily focused on engagement with the Angular community through education. But in this week's episode, we won't be learning anything new; we won't hear from a community expert about a particular technology; we won't discuss the past, present, or future of Angular; and we won't learn about state management, flux, redux, NgRx, or RxJS...You might be asking - "Well, then what ARE the wonderful panelists going to talk about on today's show?"In the first installment of the Angular Sideline, our lovely panelists Jennifer Wadella, Aaron Frost, & Brian Love, brought you into a range of their hysterical and odd musings. And you can expect nothing different for this second episode. Just ask yourself this - "How much do you love Angular and just how far would you go to express that love?" We won't give away any of the juicy nuggets of comedy that are about to caress your ears and tantalize your neurons. Just click play - and don't forget to subscribe so you don't miss any of our future episodes of the Angular Show.Jennifer Wadella @likeOMGitsFEDAYBrian Love @brian_love@aaronfrostShow Notes:https://twitter.com/zackderose/status/1315647734729248768
Let's admit it - sometimes CSS can be difficult. Seasoned veterans of web development even struggle with CSS. It's this magical thing that makes our applications look and work with beauty. But, it can also be a challenge, especially as our applications and teams grow and evolve. Most Angular developers spend their day writing TypeScript, HTML, and CSS, or potentially use a preprocessor for CSS such as SCSS or LESS. This episode of The Angular Show focuses on the latter.The panelists are joined by Nicole Oliver, a senior software engineer at Narwhal, who teaches about styling applications in Angular as she shares her experience working with large organizations to reign in the beast that is CSS.The group dives into topics such as block-element-modifier (BEM), Scalable and Modular Architecture for CSS (SMACSS), Object-oriented CSS (OOCSS), and utility-first methodologies. They also chat about using SCSS variables, CSS custom variables, and other approaches for consistent styling of Angular applications.Nicole Oliver @nixalloverJennifer Wadella @likeOMGitsFEDAYBrian Love @brian_loveAaron Frost@aaronfrostShow Notes:Material.iohttps://material.io/design/material-studies/fortnightly.html#product-architecture
RxJS provides both the observable primitives as well as a broad set of operators for the creation and transformation of data. And, as you know, Angular leverages RxJS for cancelable asynchronous actions and events. In our opinion, the two are a perfect match. Interactions with web applications are asynchronous in nature and Angular provides a robust solution to detecting those asynchronous actions, enabling developers to build interactive experiences for the web with ease.In this series on RxJS operators, we help you learn the operators. As you likely know, there are a lot of them, and it can be difficult to know what each of them does, and often, how to determine which operator, or operators, are succinct and current for solving the complexities of streaming data, actions, and events in our applications.Join panelists Jennifer Wadella, Aaron Frost, Brian Love, and guest Jan-Niklas Wortmann as we explore the creation operators. These functions enable the creation of new observables, or the composing of existing observables into a new observable stream. Jan-Niklas is a Google Developer Expert in Angular and volunteers his time on the RxJS core team. Listen in and learn from Jan-Niklas as he teaches us about many of the creation operators in RxJS. We're sure you'll walk away from this episode with a new and expanded knowledge of RxJS.Find us on Twitter:Jan-Niklas Wortmann | @niklas_wortmannBrian Love | @brian_loveJennifer Wadella | @likeOMGitsFEDAYAaron Frost | @aaronfrost
Grab your favorite cola, some swig, a beer, or sangria, and sit down with panelists Jennifer Wadella, Aaron Frost, and Brian Love for a hangout. This week's episode of The Angular Show is about the show. It's a bit meta, we know, but we wanted to share with you a little bit about why we spend a few hours every week to create the Angular Show. This podcast was born out of a desire to make a podcast that reflects the community, that is inclusive, and that is welcoming.We also wanted to share with you some of the funny moments that have occurred both before and during the show. We can't give away the herbs and spices that make up the secret sauce that coats the delicious podcast that tantilizes your ears, but (hint, hint) we offer a slight possibility of leaking some of the juicy bits if we get enough tweets on the 'ole Tweet Machine.Finally, we share with you how we pick our guests and how we determine the topics that we talk about. We also shared how we transitioned the show this year to focus on producing several series, with more in depth series yet to come on topics such as forms.
Panelists Jennifer Wadella, Aaron Frost, and Brian Love sit down with Lukas Ruebbelke, a Google Developer Expert in Angular, author, speaker, and mentor, to learn about a mentorship model that Lukas has developed for providing individuals with the opportunity to change their lives through programming. Lukas has displayed his love for the community through deep personal investments using his mentorship model. Starting with his first-principles and cross-pollination approach to software development, Lukas teaches with passion and heart. Throughout the history of software engineering, the tools, languages, and frameworks have changed drastically. However, what has not changed, as proposed by Lukas, is that programming can be distilled to four first-principles: nouns, verbs, iterators, and conditionals. Taking this one step further, Lukas teaches about what he refers to as the "axis of evil", which is when it is too painful to write tests for your code. The panelists and Lukas talk about what it means to write good code, and how this varies based on the context of good code.To wrap things up, Lukas and the panelists talk about investing in ourselves and the people with whom we interact, in our organizations and the community. It's important that we take the long game to software engineering and prioritize our own mental health and our relationships.Show Links:https://osmihelp.org/resourceshttps://www.amazon.com/Infinite-Game-Simon-Sinek/
In this episode of the Angular Show, panelists Brian Love, Aaron Frost, and Jennifer Wadella sit down with the team at Infragistics, the creators of Ignite UI, a complete UX/UI toolkit for building high performance, modern web, mobile, and desktop applications.The team at Infragistics has a long history of developing desktop applications using Microsoft technologies for enterprises and has worked with clients to move legacy applications to the web. This is where Angular comes in - as a perfect match for building robust and scalable line-of-business applications. Using Ignite UI and Angular, the team at Infragistics is able to efficiently bring desktop applications to the browser.Enterprises rely on applications that are secure, tested, scalable, and will meet the demands of the future. Infragistics provides solutions to meet these requirements. To learn more go to https://www.infragistics.com/products/ignite-ui.Show Links:► https://github.com/johnpapa/HotTowel► https://twitter.com/gabsmashh/status/1301153985592733696► https://twitter.com/AdamRackis/status/1300855838828040197► igniteui.com► github.com/igniteui►Video series on Desktop web: https://www.youtube.com/watchv=TAaG0nUUy6A&feature=youtu.be► vote.govBrian Lagunas: @brianlagunasKonstantin Dinev: @KonstantinDinevSteve Johnston: @stevenMJohnston
What is the future of Angular? What new features and improvements are being thought of and worked on? Will the developer experience improve? Panelists Brian Love and Aaron Frost sat down with Minko Gechev, a member of the developer relations team for Angular at Google and a longtime contributor to Angular through open-source, to answer some of those questions. And trust us, the future of Angular is bright, starting with all the amazing new features that are being built. The developer experience is only going to get better and faster. Minko shares with us a look into the potential future of Angular. Minko shares with us a look into the potential future of Angular, including the future support for TypeScript 4 versions. The Angular team is committed to supporting future TypeScript versions that bring new features, improvements, and fixes to the language. We then learn about the transition of the Angular Language Service to leverage Ivy, the compilation and rendering engine shipped in Angular version 9, which will solve some inconsistency issues, but also provide some speed improvements in our IDE. We also learn about the migration that is going to happen from TSLint to ESLint, and what that transition is going to look like. Minko then discusses how the team is going to tackle the inlining of critical CSS in order to improve an application's First Contentful Paint time. Finally, we learn about a new and exciting developer tools extension that is going to help Angular developers to profile and inspect their applications.Today, Angular is an incredible framework and platform for building web, mobile, and desktop applications, and we're excited by the outlook and possibilities moving forward! Listen in and join us as we get a sneak peek into that future.Show Notes:► https://twitter.com/MikeRyanDev/status/1307687779195854849► https://github.com/angular/angular-cli/releases/tag/v10.1.0-next.7
As a follow-up to Ep. 020 - Building Communication Between the Angular Team & the Community - we sat down with Stephen Fluin and Jules Kremer of the Angular team to continue the conversation on the present and future of Angular. You can check out Ep. 020 right here 👉 http://bit.ly/AngularShowEp20Show Notes:► https://blog.angular.io/a-roadmap-for-angular-1b4fa996a771
State management is hard. Why? First, some engineers may not consider the state of their apps. This can lead to apps that are buggy, difficult to test, and often face regressions when attempting to fix issues. Second, if you're managing control flow and state in your application, state in some applications can be complex and fast-moving. Determining what solution to use, whether to build your own solution or to grab an existing off-the-shelf solution can be a difficult decision. Third, state management libraries can be difficult to learn. Entire courses are devoted to managing state in Angular applications, whether you choose NgRx, NGXS, Akita, MobX, Redux-Observables, etc.We get that. Why? We've seen a thing or two. In this episode, panelists Jennifer Wadella, Aaron Frost, & Brian Love share some of their own struggles with state management, decisions that went awry, and some horror stories that they've lived through. Then, Brian sits down with Mike Ryan, core team member for NgRx, and Google Developer Expert in Angular. Mike shares with us some stories and some key takeaways for managing state, control flow, and code volume in your Angular application using NgRx.And that's a wrap! We hope you've enjoyed our 6-part series on State Management in Angular. What topics interest you that you'd like us to dive into on the Angular Show? Let us know! Follow us on Twitter, our DMs are open, and don't forget to subscribe!
loading
Comments (2)

ZeRonaldo89

something is Off this is the Reactive Form episode

Mar 10th
Reply

ZeRonaldo89

Frosty is the best "Dont talk trash about template driven forms" made my day

Mar 4th
Reply
Download from Google Play
Download from App Store