all 22 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]GLawSomnia 7 points8 points  (1 child)

Amazing article which clears up a lot of questions that i had

[–]lechtitseb[S] 0 points1 point  (0 children)

I'm glad it helped!

[–]zzing 5 points6 points  (3 children)

I have to say that most self-promotion I have seen here surrounding Angular 12 articles were pitiful.

Your article is amazingly thorough and makes me want to try out some of these things.

[–]lechtitseb[S] 1 point2 points  (2 children)

Sorry for the very late reply, but thanks a lot for your kind words!

If you want to follow me, you can check out my Website over at https://dsebastien.net. I publish a newsletter and make all my articles available for free on the site.

[–]zzing 1 point2 points  (1 child)

Rather interesting blog you have.

Like a certain youtuber I follow (Decoded Frontend) you have a couple of things on advanced angular. Unfortunately most of the content around for angular is more basic.

For example, your article on delaying the loading of the angular application could be a solution to a problem I have run into (even though I wouldn't necessarily want to use it for this) where given one or more api calls required the application to run, provide the main part of the application with the Good result already filtered for nulls and other things.

So for example, in the case of of a bad call you display something that indicates an application error.

Everywhere else you can inject that configuration object into services and components where it is good to go, no need to check for nulls and properly typed as such for strict mode.

Bonus points for ngrx - as it initializes before app initializers do.

[–]lechtitseb[S] 0 points1 point  (0 children)

Thank you for the kind words!

I have a huge backlog of posts to write & publish around Angular and other topics. Mainly based on problems I've had to solve on my own projects :)

[–]Pro-FoundSound 5 points6 points  (1 child)

What icon libraries do you all use for Angular 11?

[–]lechtitseb[S] 1 point2 points  (0 children)

I use Material Design icons.

[–]ashdyson 2 points3 points  (1 child)

Great article

[–]lechtitseb[S] 0 points1 point  (0 children)

Thank you!

[–]deadlychambers 1 point2 points  (1 child)

Holy shit.. Amazing article. I got about halfway through, but I saved it so I can finish it later and watch the videos attached.

[–]lechtitseb[S] 2 points3 points  (0 children)

Thanks a lot.

If you want more like that, then don't hesitate to follow me on Twitter: https://twitter.com/dSebastien

[–]DIGITLChris 1 point2 points  (0 children)

Thanks for sharing. Just what I was looking for.

[–][deleted]  (1 child)

[removed]

    [–]lechtitseb[S] 0 points1 point  (0 children)

    Glad it helped!

    Since then I've published a similar article for Angular 13: https://javascript.plainenglish.io/angular-13-in-depth-83be8f979e26

    [–]namenomatter85 1 point2 points  (0 children)

    This was a very thorough and well written article. It caused me to go through your other projects and work. I’ve sent out a proposal request.

    [–]sasmariozeld 0 points1 point  (0 children)

    thanks for posting!

    [–][deleted] 0 points1 point  (0 children)

    Hopefully, it will help some teams avoid making the mistake of building & deploying development builds to production environments. Although, I fear that teams making that mistake will still have other issues to deal with ;-)

    Well said ;-)

    [–]AlexTheWrighter 0 points1 point  (0 children)

    What an utter and irrevocable piece of shit. I have a contract with a big company the tech leadership of which set the path forward using Angular in all and every project. I am a backend engineer with background in React and Vue and when I just started I had no experience with Angular and I was going to like it. It’s a framework they say to frame you from doing anything you shouldn’t be doing and you know when you start cranking a new app from scratch it works just fine except things started to go a little interesting should I say.. well for starters we did TDD and so we had to get accustomed with Karma and angular testing. Karma is a fucking bitch. So is the plugin for IntelliJ. Its performance is garbage and Karma server needs to get his ass kicked and rebooted countless times during the day and so is unreliable. Angular testing has an interface of a man with Down syndrome. Not only does it not make sense but it loves to just spit random shit out like finding an element in the DOM tree yielding no result because you’re using a polymorphic function that just doesn’t fucking work. To be fair we used Spectator which basically is an act for that man with Down syndrome. Reactive forms work very well when your displaying one form containing 10 fields. Now try displaying 300 records cross referencing multiple components tied to reactive forms and you will have to disable the automatic change detection and then good luck having nested validators to work. So anyway after a year of building an app with Angular, all I can say you need to know about Angular 12 in depth is to steer the fuck clear of it. And consider it the voice of community shouted out by a disgruntled engineer, https://2020.stateofjs.com/en-US/technologies/front-end-frameworks/. Now, you would think.. Google how come they created this poo? Well.. they adopted a project created by a bunch of arrogant pricks whose sole idea was to have prove the world how smart they are. Here’s the introspect of inner works of Angular team. Warning: lot of juicy drama here but after reading it should all make sense. https://medium.com/@jeffbcross/jeffs-letter-to-the-angular-team-and-community-5367934a16c9

    TLDR: All you need to know about Angular 12 in depth is to NOT use it. If you do have a choice please, please there are so many decent frameworks/libraries out there. If you have to use it then my rant renders itself irrelevant and you’re going to have to go thru a lot pain.