Big lover of RxJS here, but to be fair, because of its (initial) complexity Angular have not been able to catch up with React's popularity. I am glad they're making it optional.
I guess that's fair. I use RxJS with React and other front-end libraries all the time. It and state machines via xstate (which by no coincidence has built-in support for RxJS) enables devs (especially component authors) to not depend on proprietary ways of managing state and event/data changes over time associated with Web app or component front-end libraries that don't transfer across different front-end libraries as much. Its use essentially as a push-based endofunctor abstracton (consistent way to reason and chain value changes over time) makes it typically a better way to handle async and synchronous over time (including collection of data) than promises and in many cases async iterables that yields promises. A Observable can do the things a promise can, but a promise can't do everything an Obsevable can. Observable is also now renewed to be available directly in browsers to compliment existing DOM event APIs as a better and more advanced way to handle events.
Unfortunately lots of old news that was already out there and not really answering the questions that the community still had on various topics. Like the state of testing tools (since deprecating Karma and Protractor it hasn't really been updated at all). Also esbuild is nice but its still outputting a bazilion files that might not work for every use case yet (especially mobile)
Something that's really interesting and not specifically highlighted is that Angular is slowly getting rid of decorators. I'm a fan of decorators but it seemed like a vulnerability for Angular. The reason is that Angular is using the experimental decorators and not the TS 5 decorators. The TS5 decorators are more aligned with the EcmaScript proposal for decorators. So I've always wondered what would happen to Angular if Typescript decides to deprecate the experimental decorators
big kudos for the new feature of Angular, but guys, please do a better presentation, avoid this sonnet recitation of three in robotic style, you're not playing Macbeth of Shakespeare
A someone who started with angular quite recently (approx 3 months), Shall I put my efforts on RXJS or not? I already see very less resources on angular and I'm not very sure about what things to go with. If anyone with some relevant experience then please leave a suggestion.
Depends on what you want to achieve at the moment. If your goal is just to learn the framework for fun/side projects/expand your view, RxJS can wait till quite a bit later. But if you goal is to become a professional frontend developer, or more specifically, Angular developer, yes, you should invest in learning RxJS. (They *will* come up in an Angular interview, if you need a more substantial reason. :) I'd suggest getting familiar with the essentials first, like data and event binding, routing, forms, DI, state management, etc. Then when you dive into the reactive style of programming, learn common RxJS operators and use cases and *unlearn* all the bad habits as you go. Async programming is difficult and tricky at the same time. RxJS is not the only tool but it does provide tools to let you deal with the async complexity more concisely. And observer pattern has been around for decades so there's nothing wrong learning about a tool that promotes and implements it. But yeah, depending on your capacity and primary goal, you should prioritize your learning wisely.
Why would we need al those features if you spend almost half of Google I/O trying to convince us that AI is taking over not only our lives but our work as well :) Just give us angular AI already.
Unfortunately, static members cannot reference class type parameters. You could have: new input().required(); But I hope we can all agree that's gross and worse than input.required();
Minko for president
Big lover of RxJS here, but to be fair, because of its (initial) complexity Angular have not been able to catch up with React's popularity. I am glad they're making it optional.
I guess that's fair. I use RxJS with React and other front-end libraries all the time. It and state machines via xstate (which by no coincidence has built-in support for RxJS) enables devs (especially component authors) to not depend on proprietary ways of managing state and event/data changes over time associated with Web app or component front-end libraries that don't transfer across different front-end libraries as much.
Its use essentially as a push-based endofunctor abstracton (consistent way to reason and chain value changes over time) makes it typically a better way to handle async and synchronous over time (including collection of data) than promises and in many cases async iterables that yields promises.
A Observable can do the things a promise can, but a promise can't do everything an Obsevable can.
Observable is also now renewed to be available directly in browsers to compliment existing DOM event APIs as a better and more advanced way to handle events.
cool to see how google team molds web, angular still the most complete framework
Unfortunately lots of old news that was already out there and not really answering the questions that the community still had on various topics. Like the state of testing tools (since deprecating Karma and Protractor it hasn't really been updated at all). Also esbuild is nice but its still outputting a bazilion files that might not work for every use case yet (especially mobile)
They are working on "automatic AI testing"
Something that's really interesting and not specifically highlighted is that Angular is slowly getting rid of decorators. I'm a fan of decorators but it seemed like a vulnerability for Angular.
The reason is that Angular is using the experimental decorators and not the TS 5 decorators. The TS5 decorators are more aligned with the EcmaScript proposal for decorators. So I've always wondered what would happen to Angular if Typescript decides to deprecate the experimental decorators
Answer.... yet another version of Angular where we end up re-writing much of our code.
Excelente herramienta de crom de Chrome, felicitaciones
big kudos for the new feature of Angular, but guys, please do a better presentation, avoid this sonnet recitation of three in robotic style, you're not playing Macbeth of Shakespeare
Great job! Waiting for optional RxJS
why ?
lol
26:00 Is there ongoing work to help ESBuild reduce the bundle size?
yes! Angular 18 will come out later this week. And they announced even better performance and bundle size reduction
who did the audio though it sounds horrible
I notice an obsession with efficiency in rendering "text", but these days what people consume most is video.
A new messup with RxJS on the way
A someone who started with angular quite recently (approx 3 months), Shall I put my efforts on RXJS or not? I already see very less resources on angular and I'm not very sure about what things to go with. If anyone with some relevant experience then please leave a suggestion.
As someone with a more clear view from the outside I say no.
Depends on what you want to achieve at the moment. If your goal is just to learn the framework for fun/side projects/expand your view, RxJS can wait till quite a bit later. But if you goal is to become a professional frontend developer, or more specifically, Angular developer, yes, you should invest in learning RxJS. (They *will* come up in an Angular interview, if you need a more substantial reason. :)
I'd suggest getting familiar with the essentials first, like data and event binding, routing, forms, DI, state management, etc. Then when you dive into the reactive style of programming, learn common RxJS operators and use cases and *unlearn* all the bad habits as you go.
Async programming is difficult and tricky at the same time. RxJS is not the only tool but it does provide tools to let you deal with the async complexity more concisely. And observer pattern has been around for decades so there's nothing wrong learning about a tool that promotes and implements it.
But yeah, depending on your capacity and primary goal, you should prioritize your learning wisely.
Why would we need al those features if you spend almost half of Google I/O trying to convince us that AI is taking over not only our lives but our work as well :)
Just give us angular AI already.
I love this new terminology, "AnguWiz"
WizAng
Angular is so awesome
The only useful part of Angular is data/ui binding in my opinion. Please see the new "features" as liabilities while they might be assets.
ang is the best
Cooooool
you could trash out rxjs from ang interceptor and other libs so we don't have to use it.
So Signals are basically events. Seems like should have been done this way from the start.
input.required () what is this syntax..it should have been input.required ()
Why?
Unfortunately, static members cannot reference class type parameters. You could have:
new input().required();
But I hope we can all agree that's gross and worse than input.required();
And again the misleading, still highly debatable, Zippy is back 😹
You know what else is new? The lack of jobs!
🫡
React and next js better
at marketing and selling themselves, true
for hobby projects, maybe.
for noobs
Fraud