@@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.
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.
@@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.
@@andreashahn9037 the problem with signals right now is that they are not fully implemented yet and are experimental, like you said with asynchronous requests: The angular http client still uses observables and has no signal support. Moving to signals is a good choice and getting rid of zone.js, but signals should with care until they are production ready.
![[EN] NGRX Signal Store - Fabian Gosebrink](http://i.ytimg.com/vi/vUWM4CerzDo/mqdefault.jpg)
![[DE] Angular Testing in 2024](/img/n.gif)
Great stuff!
That being said, the innnovation section at 7:20 is close to perfect, things are moving in the right direction
Jesus lord, I hope for the love of God they don't waste their resources on AI
IMHO, there is a lot of potential for using AI for migration scripts, as LLMs are pretty good with source code.
@@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.
@@hendrx Absolutely agree. It's a productivity boost in some cases.. It's a stack-overflow on steroids.
@@LarsRyeJeppesen it's a code snippet generator at this point
Bad bad bad , a lot of changes and angular is becoming unpopular
Do not add signals
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.
@@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.
@@andreashahn9037 the problem with signals right now is that they are not fully implemented yet and are experimental, like you said with asynchronous requests: The angular http client still uses observables and has no signal support. Moving to signals is a good choice and getting rid of zone.js, but signals should with care until they are production ready.