33:30 - Action wrapper - also known as the "facade" pattern in OOP land. 🙂

thanks a lot !

😂 brilliant! The dev world definitely missing more talks such as the last part. Although it was truly by accident, I'm happy I found it... Thank you!

Navigating to a web socket url in chrome -> disallowed url scheme 🎉

Кал

Oh RxJs is so evil and soooo dificult Mi mi mi...All crybabies and just bad developers. RxJS is a great tool. Frontend Development is by nature reactive thats why RxJs is a great fit!!!

Great @Manfred. Is it possible resilient header and footer on shell, just call loadChildren with another and header and footer default for all?

Very helpful. Thanks a lot!

Great!!😃

For those who haven't read the book and watch this video. First, read the book Domain-driven Design by Eric Evans. The language is ubiquitous, it is a property of the language of the domain or the bounded context. It means it permeates everything, discussions, documents, diagrams, and the code itself!

I am following your guidance to use Docker, and then you switch to bitnami because the docker does not work. WTF!! I am wasting my 20 minutes here

The advice in here is literally that it is not possible to have too many modules. I mention it as a quick way to assess the guidance as a whole.

Thank you for sharing

Du bist der Hammer, Golo!

i agree with you, that not everything needs to be pressed in the rxjs pattern. single one-time calls are perfect for promises. i also agree on the less modules. it leeds to over-engineering

That was so great hour, thanks a lot!

loadManifest for nested microservice front end is not loading ex shell loadsmanifest --->mfe1 loadsmanifest ---->mfe2 but mfe1 cannot bootstrap manifest file

I know the video is years old I cannot find the slides

Thanks. Very clear separation of all concerns :)

Thank you

Great explanation @Manfred. Is there any example of standalone Angular components which are rendered on the same route? I only found one component per route, but what if we have case when we want to render multiple MFE-s which are actually standalone components - but on the same route?

source code

useless tutorial man... you just show how to install wordpress locally and activate a plugin?! where is the connection to angular?

I had to stop the moment she started discussing threading. This is the dumbest take on threading in other system. She is batshit crazy to say that 1000 request will be processed in 1000*10 mb just the stack memory. Not even database server works this way. What a dumbass video I had high hopes

I am interested in using module federation for a new project, however I am struggling with the idea of web components and how they would be used or fit in conjunction with module federation. I am pretty new to the UI space having been a backend developer for pretty much all my years. If I had a shell app, I could import a child web component (or even an entire app) by importing the web component js from its deployed path. But I could also do the same with module federation and webpack? Could someone help me understand why one would use both, or would you pick one solution, or do they work together? I am finding it hard to conceptually differentiate between the two. Ideally I want to be able to compose some MFEs with in shell/host app, with apps built by other teams.

Thanks for the conversation. Was useful, as I am learning back-end development! Thank you!

Best !

I am scared to disable the zone-js in the existing applications.

at 25:00 using simple promises helped in downloading file. Because it was one time thing and single. There was no way to use async pipe for it in the template. If I use promise for this purpose, I don't need to clean it.

Meaty and mind bending. Thank you.

I have to disagree with the "There are no bad practices" point. There are, and I have been screwed over by some in quite a few legacy projects that I need to maintain. The KISS principle is great, but I think many people mess up the two concepts of "simple" and "easy," and I am afraid that Nir's first part on modules is a bit misleading here. When the problem that an app is trying to solve is simple, keeping things all together is ok. Heck, you may not even need a framework for that, let alone something like Angular. However, when the problem and its business domain get complex, one has to split things up, either vertically or horizontally, or most likely, both. You don't include everything in the initial bundle (putting everything in a single module) because it's easy. You don't include a bunch of function calls that deal with business logic in the template because it's easy. These easy practices hurts maintainability, and I don't think we should lower the bar when it comes to architecture just because we are dealing with the frontend.

How do you use perf_hooks with async/await paradigm in AWS Lambda functions? Lambda functions stop processing the event loop when you return from the event handler, so you want to await whatever you need to make sure that all of your processing is finished before returning from the handler. The PerformanceObserver appears to be event based and can be set up to use buffers, but how can you be sure that you've processed all of the messages? Thank you very much for the video!

Nice basics.

Thank you 🙏

Near the end, I really thought he will have a heart attack

This talk is honest. May be a little bit too honest coming from an Angular insider. But every point Nir says is blatantly true. The angular team seems to be focussed on complicating Angular more and more to push it to do all things at once making it difficult to learn and to code... But the only way to make angular better is to reduce the complexity and leave it to the developers to add complexity where and when needed. Just by reducing the dependency on RxJS and better managing the change detection and removing unwanted dependencies Angular will be 100 times better than the other frontend frameworks/libraries out there.... But it seems unlikely...

Angular-KISS should become an Angular Community!

I agree you should use Angular in the simplest possible way! (do not use all the whistles and bells of Angular from the begin of your project) Have a simple Angular Mental Model: Angular is 5D: Directives - Data Binding - Dependency Injection - Decorators - Dirty Checking! or Angular is a huge Template Engine: Angular starts with the Template (the my-component.html is not HTML it is a template with <ng-template> ... </ng-template>!

The Advantage of RxJs is: once you are in the RxJs World with a creation Observable (interval, of, range,...) you can stay in this world for all your logic and when you want to run the RxJs Pipeline you built (RxJs programming is building a Pipeline of functions (operators) you subscribe to the pipeline!

Very good explanation. Patience is a Gift. Agree :)

Great talk, always clear and prompt. Very good to also repeat the questions asked.

two hundred first bleat'!

As someone who works with clients (both users and browsers) and deals in accessibility, one of the most frustrating surprises of my job is having to convince devs "simple is not a dirty word."

Does Smashing Magazine generate every single article on every single build?!

Excelent video! thank you very much.

I am looking to share services and make them as singletons to be used between my shell and micro front ends in angular. I use angular architects module federation! I have multi repo MFEs so NX share libraries would not be a good option. Any advise?

Very well explained! Thank you ser 🙏🌹

That was awesome!! thanks for sharing

What a teacherrrrrrrr💚