Manfred Steyer
Manfred Steyer
  • 69
  • 95 899

Відео

Angular: Future Roadmap
Переглядів 2,4 тис.Місяць тому
Angular: Future Roadmap
Let's go Zoneless - Matthieu Rieger at Angular Graz, Summer 2024
Переглядів 597Місяць тому
Let's go Zoneless - Matthieu Rieger at Angular Graz, Summer 2024
NGRX Toolkit, Rainer Hahnekamp, GDE
Переглядів 8657 місяців тому
NGRX Toolkit, Rainer Hahnekamp, GDE
The state of change detection in v17, Matthieu Riegler
Переглядів 1,6 тис.7 місяців тому
Change detection is one of the core features of every framework. This feature is responsible for updating the DOM when the state of the app changes. Most of the time, change detection is a performance-sensitive matter, and knowing in detail how it works will help you get the best out of it. With the rise of Signals and recent work toward the official support of Zone-less apps, let's have a look...
Angular Best Practices, Sam Vloeberghs
Переглядів 3,1 тис.7 місяців тому
Angular has come a long way since its inception and the release of v2 a little over 7 years ago, in 2016! Best practices were part of the framework's core from the start and have evolved over time. Let's explore the best practices that are promoted from inside the framework today. Let's learn how they can ease the work for developers in creating and maintaining secure, accessible, and performan...
NgRx SignalStore: In-Depth Look at Signal-Based State Management in Angular by Marko Stanimirović
Переглядів 6 тис.8 місяців тому
NgRx SignalStore: In-Depth Look at Signal-Based State Management in Angular by Marko Stanimirović
Meetup: The Future of Angular
Переглядів 1,4 тис.Рік тому
Meetup: The Future of Angular
[EN] Meetup: The Future of Module Federation
Переглядів 2,1 тис.Рік тому
[EN] Meetup: The Future of Module Federation
Sustainable Angular Architectures With Strategic Design and Nx @AngularMittelfranken
Переглядів 5904 роки тому
Sustainable Angular Architectures With Strategic Design and Nx @AngularMittelfranken

КОМЕНТАРІ

  • @helloworlditsworld
    @helloworlditsworld 3 дні тому

    Don’t tell my wife but I seriously love you man! Haha thank you for the content and information

  • @GLawSomnia
    @GLawSomnia 6 днів тому

    Ok this was one of the best talks i have ever listened to. Will tell my coworkers about implementing an BFF

  • @ManfredSteyer
    @ManfredSteyer 6 днів тому

    Angular Security Workshop with Philippe De Ryck: www.angulararchitects.io/en/training/angular-security-with-dr-de-ryck/

  • @stanislautsishkou5632
    @stanislautsishkou5632 7 днів тому

    Sounds like signals are always a state of data, and it is not possible to make a decision for invoking data change based on data state, the concept of `view = function(state)` is broken in such case. Data could not have an intention to be self changed (via `effect`), because behaviour is not a data or state feature. Behaviour that based on Action/Event is a missing part of signal architecture

  • @alexander.thalhammer
    @alexander.thalhammer 8 днів тому

    We're here in Styria -> we're distilling everything 🤣🤣🤣

  • @philippjohn555
    @philippjohn555 11 днів тому

    Nice talk as always.

  • @alinghinea98
    @alinghinea98 12 днів тому

    first time I see the injections with # prefix. Is there a convention on why did you write it like that?

    • @ManfredSteyer
      @ManfredSteyer 12 днів тому

      Not really. It’s the official ecmascript syntax (es2022) and I decided to use it in this example. Saying this, the TypeScript private also has several benefits: it’s easier to debug (because it’s actually public after transpiling to JavaScript) and it comes with no performance overhead at runtime (for the same reason).

    • @alinghinea98
      @alinghinea98 12 днів тому

      @@ManfredSteyer Thanks for clarification :)

  • @LarsRyeJeppesen
    @LarsRyeJeppesen 12 днів тому

    This was great. Love signals, but having to use untracked() heavily lol

    • @ManfredSteyer
      @ManfredSteyer 12 днів тому

      I totally feel you. Using untracked or some wrapper around it like a custom explicitEffects helper or toObservable really helps to see what’s going on and to avoid issues.

  • @superduper1211
    @superduper1211 12 днів тому

    awesome . thank you for sharing

  • @ManfredSteyer
    @ManfredSteyer 12 днів тому

    Angular Architecture Workshop: www.angulararchitects.io/en/training/advanced-angular-architecture-workshop/

  • @LarsRyeJeppesen
    @LarsRyeJeppesen 24 дні тому

    Great stuff!

  • @hendrx
    @hendrx Місяць тому

    That being said, the innnovation section at 7:20 is close to perfect, things are moving in the right direction

  • @mayori-engineering-hub
    @mayori-engineering-hub Місяць тому

    Do not add signals

    • @LarsRyeJeppesen
      @LarsRyeJeppesen 24 дні тому

      Signals is the best thing that ever happened. What are you talking about ? ALL frameworks are moving (or have moved) to signals, and that is with a good reason. Fine grained change detection is amazing. Ditching zoneJS is amazing. I can't imagine not using signals by now.

    • @andreashahn9037
      @andreashahn9037 24 дні тому

      @@LarsRyeJeppesen Signals are not the best thing and should not be used for everything. The second you need some asynchronous data it becomes a hassle with computed -> toObservable -> toSignal etc. They solve a tiny thing but people misuse them already.

  • @mayori-engineering-hub
    @mayori-engineering-hub Місяць тому

    Bad bad bad , a lot of changes and angular is becoming unpopular

  • @hendrx
    @hendrx Місяць тому

    Jesus lord, I hope for the love of God they don't waste their resources on AI

    • @ManfredSteyer
      @ManfredSteyer Місяць тому

      IMHO, there is a lot of potential for using AI for migration scripts, as LLMs are pretty good with source code.

    • @hendrx
      @hendrx Місяць тому

      @@ManfredSteyer LLMs are just a hit or miss when it comes to code, I have yet to find a task of mine that has been taken over by AI code generators, that's if you're a senior of course.

    • @LarsRyeJeppesen
      @LarsRyeJeppesen 24 дні тому

      @@hendrx Absolutely agree. It's a productivity boost in some cases.. It's a stack-overflow on steroids.

    • @hendrx
      @hendrx 24 дні тому

      @@LarsRyeJeppesen it's a code snippet generator at this point

  • @mann_von_welt
    @mann_von_welt Місяць тому

    Thanks for sharing, looking forward to going zoneless in our next project!

  • @peterchapman6210
    @peterchapman6210 2 місяці тому

    Thankyou, This looks brilliant! I too really am a fan of the original global store, and redux pattern, and the devtools. When using the other stores, such as component store, I essential thing I really missed was the the devtools, as they have been a life saver to me in the past when debugging and tracking what actions change the state. This would be worth it just for the devtools, but now also with this redux pattern as well, this will really could convince me to swap from the global store over to the signal store.

  • @koempf
    @koempf 3 місяці тому

    wie ist das mit dem Feature withDevTools in production Mode... ich muss den Toolkit ja unter "dependencies": { installieren, weil ich ja evtl. withcallState verwenden möchte. In Produktion möchte ich aber nicht die Devtools sehen ?

    • @RainerHahnekamp
      @RainerHahnekamp 3 місяці тому

      Hast recht. Es gibt da eine schnelle und eine etwas längere Lösung. Die schnelle ist ein Flag, wo du es während der Produktion nicht läuft, aber das JavaScript trotzdem im Bundle ist. Die lange ist, dass es auch aus dem Bundle fliegt. Das wird ein bisschen knackiger. Kannst du fürs erste Mal mit der schnellen Lösung leben? Installieren musst das toolkit natürlich in dependences (hast eh schon erklärt wieso).

    • @koempf
      @koempf 3 місяці тому

      @@RainerHahnekamp Hi Rainer :-) super danke für die schnelle Antwort... das Flag muss ich dann selber in meinen Store einbauen? oder gibt es das irgendwo ? liebe Grüsse :-)

    • @RainerHahnekamp
      @RainerHahnekamp 3 місяці тому

      @@koempf Serwas, nein das gibts noch nicht. Das müsste ich noch machen. Wäre super, wenn du mir einen Issue auf GitHub anlegen könntest. Dann hab ich einen offiziellen "Arbeitsauftrag". Falls nicht, kanns aber ich auch so machen.

    • @koempf
      @koempf 3 місяці тому

      @@RainerHahnekamp super ich mache einen Eintrag :-) noch kurz eine letzte Frage :-) bei der standalone patchState function... da muss ich bei Objekten immer die immutability beachten ? ich wurde da bei einem internen Vortrag gefragt ob es dafür eine Library gibt um das nicht immer machen zu müssen 🙂

    • @RainerHahnekamp
      @RainerHahnekamp 3 місяці тому

      @@koempf ja, gibts: github.com/timdeschryver/ngrx-immer. Wir werdens aber auch im toolkit irgendwann aufnehmen.

  • @LeonhardPfeiffer-Friedl
    @LeonhardPfeiffer-Friedl 3 місяці тому

    4th Option: Jasmine/Jest for everything with @puppeteer/ng-schematics

  • @harrymiller7559
    @harrymiller7559 3 місяці тому

    a train, that is too fast. 🙂. In germany this will never happen.

  • @krzysiekpiasecki
    @krzysiekpiasecki 4 місяці тому

    The summary of our Dev conclusions. Thanks.

  • @amitev
    @amitev 4 місяці тому

    51:21 Servus, is there a reference to the Playwright initiative so we can see what has happened with it?

  • @yelose85
    @yelose85 4 місяці тому

    Please!! Could you make a video or a course explaining how to test AngularFire within a standalone app? like firebase authentication or firestore?. Thank you

  • @LarsRyeJeppesen
    @LarsRyeJeppesen 4 місяці тому

    This was great. Reminds me to implement webauthn on our internal site.

  • @ManfredSteyer
    @ManfredSteyer 4 місяці тому

    Angular Architecture Workshop: www.angulararchitects.io/training/advanced-angular-architektur-workshop/

  • @RainerHahnekamp
    @RainerHahnekamp 4 місяці тому

    Here is the link to my slides: speakerdeck.com/rainerhahnekamp/towards-modern-change-detection

  • @alexander.thalhammer
    @alexander.thalhammer 4 місяці тому

    Seems like my hair was a bit excited at the beginning 😀

  • @ManfredSteyer
    @ManfredSteyer 4 місяці тому

    Source code at github a at: boudard/springboot-module-federation

  • @ManfredSteyer
    @ManfredSteyer 4 місяці тому

    Source Code provided by Alain: github.com/aboudard/springboot-module-federation

  • @AlainBoudard
    @AlainBoudard 4 місяці тому

    I'd love to be able to post the url of the repo, but my comments keep being deleted.

    • @ManfredSteyer
      @ManfredSteyer 4 місяці тому

      Seems like it worked now. Please see my comment outside of this thread.

  • @AaronScribner-qj5qs
    @AaronScribner-qj5qs 4 місяці тому

    Is there a code repo for this?

    • @AaronScribner-qj5qs
      @AaronScribner-qj5qs 4 місяці тому

      The interviews are good, but without having reference source code to read and follow, these are of no interest to me.

    • @dannyvenier4728
      @dannyvenier4728 4 місяці тому

      @@AaronScribner-qj5qs he points to his github at aboudard for the angular-module-federation project

  • @AlainBoudard
    @AlainBoudard 4 місяці тому

    Thanks a million Manfred for having me ! It was a pleasure to share with you !

  • @ManfredSteyer
    @ManfredSteyer 4 місяці тому

    Angular Architecture Workshop: [English] www.angulararchitects.io/en/training/advanced-angular-architecture-workshop/ [German] www.angulararchitects.io/training/advanced-angular-architektur-workshop/

  • @VinitNeogi
    @VinitNeogi 5 місяців тому

    Angular Renaissance 🚦

  • @LarsRyeJeppesen
    @LarsRyeJeppesen 5 місяців тому

    Am using Angular 18 next 5 with the zoneless changedetector, so far working like a charm. Super exciting.

  • @LarsRyeJeppesen
    @LarsRyeJeppesen 5 місяців тому

    Awesome stuff

  • @ManfredSteyer
    @ManfredSteyer 5 місяців тому

    Modern Angular Workshop www.angulararchitects.io/en/training/modern-angular-workshop/

  • @rockenOne
    @rockenOne 5 місяців тому

    sensational stuff

  • @LarsRyeJeppesen
    @LarsRyeJeppesen 5 місяців тому

    Great stuff, thanks. Excited for what is coming

  • @arung007
    @arung007 5 місяців тому

    Great talk, lot of insights around test development

  • @StephenMoreira
    @StephenMoreira 5 місяців тому

    Great talk.

  • @edwardezekiel5358
    @edwardezekiel5358 5 місяців тому

    Awesome video Manfred and Rainer! I think this is a perfect follow-up to Alex's GitHub comment in February about TestBed/effects. I've been a proponent of skipping TestBed for unit tests, but I've come around to the "Testing Trophy" model focusing on component tests, particularly using Playwright. I still prefer to skip TestBed for Services and Pipes though just to help keep things simple.

  • @LarsRyeJeppesen
    @LarsRyeJeppesen 5 місяців тому

    Very informative, thanks

  • @SauderAndre
    @SauderAndre 5 місяців тому

    Danke euch viel mal für den wirklich sehr informatieven Beitrag.

  • @ManfredSteyer
    @ManfredSteyer 5 місяців тому

    Workshop: Professional Angular Testing -- Playwright Edition www.angulararchitects.io/en/training/professional-angular-testing-playwright-edition/

  • @ManfredSteyer
    @ManfredSteyer 5 місяців тому

    Workshop: Professional Angular Testing: Playwright Edition www.angulararchitects.io/training/professional-angular-testing-playwright-edition/

  • @1986dt
    @1986dt 6 місяців тому

    What kind of approach was used to share state between angular shell and react mfe?

  • @hardikpatel5286
    @hardikpatel5286 7 місяців тому

    @alejandroramirezjimenez757 Great Insight. Curious to know, how does web components and module federation works togather?

  • @lukasmachetanz4910
    @lukasmachetanz4910 7 місяців тому

    And is there something planned regarding the management of suspense states, hence having information regarding loading and error states out of the box? Could something like this be easily built using custom features?

    • @PlerbyMcFlerb
      @PlerbyMcFlerb 6 місяців тому

      I have the same question. Wondering if there's a way we can defer initialization and hand the signal store an initial state. Otherwise I'd end up with optional properties everywhere which feels wrong.