Time to go back home after two weeks of travel and speaking about @angular.dev . Thnx for having me @angularconnect.com and WhatTheStack conference! Got a couple more talks lined up this year but that's a story for another post.

I'm so happy that @trueadm.dev shares his learnings in the open. There are 2 problems very close to my hart being explored here: - reactivity / rendering dance; - modern authoring format. Some will claim that UI fwks are "solved problem". I don't agree. There is still so much room for improvement!

Putting finishing touches on my "Angular: framework of the future" talk (wts.sh/sessions/8iw...) for @what_the_stack conference. Arriving a few days earlier to explore Skopje was a great move - loving it here!

Tune to this one if you've got a chance. We will be sharing some LLM-related tools and techniques that I'm particularly interested in atm.

We did lots of experiments with LLMs generating @angular.dev code. They are _great_. Totally should be part of the #Angular community, proudly wearing a #Angular T-shirt.

LLMs are _really_ good at writing code - not a news at this point. What I find more interesting is LLMs used as beta-testers for new APIs and DSL: - start with idea + docs + examples - LLM-generate lots of code - see what and how it fails. It seems like LLMs tend to fail _similarly_ to humans 1/2

I've got so many great memories from the previous editions of #AngularConnect and couldn't be happier to see it happening again. The hardest part of it all: select keynote material. With so much stuff happening in #Angular we will need to do some ruthless "scope cuts" - a good pb to have I guess?

Yep, the Chrome DevTools Perf panel extension point is _great_. We clearly saw its potential and this is why @angular.dev ships with the tight integration. More info in developer.chrome.com/blog/perf-pa...

Vercel's new AI SDK 5 introduces support for Angular so you can supercharge AI-driven development with the latest Angular features 🚀 Blog post: vercel.com/blog/ai-sdk-5 Code sample: github.com/vercel/ai/tr...

📢 We're finally looking to ship Observables in Chrome!! It's been a long time coming—many thanks to all in the community for the great feedback and help along the way!! Especially @benlesh.bsky.social, @keithamus.social, @domenic.me, @jordan.har.band & more! 🙏 groups.google.com/a/chromium.o...

I'm so happy someone captured Angular's story in a documentary! This 15+ year tale is summarized in just an hour... This video shares a glimpse into the project into which we have poured thousands of hours of love and dedication. Enjoy! www.youtube.com/watch?v=cRC9...

I wish this would be a more universal knowledge. I've profiled hundreds of apps. None of them was anywhere close to the tech limits. Perf of all was improved by relatively simple treatment of removing obvious bottlenecks. Most of those apps were never profiled until someone complained....

There is so much passion, energy and history behind @angular.dev. There are many ways to tell its story and different people will have different stories. But I can very much identify with the story told in the Angular documentary: www.youtube.com/watch?v=nONH... Humbled and proud to be part of it!

I own large part of my IT knowledge to the books published by Manning. But is is very special, and I must say - somewhat surreal - to see a book that talks about concepts and APIs that I've co-designed. "Modern Angular" by @armandotrue.bsky.social www.manning.com/books/modern...

Yay, hi @angular.dev !

Wake up friends, we just dropped a new video! 🔥 If you're using Observables and Angular, you'll love this discussion about the future of Observables featuring @domfarolino.com (Chrome Team) plus @synalx.bsky.social, & @pkozlowski.bsky.social (Angular Team). #WeLearnTogether 🤓 youtu.be/ZXnwj1B29oc

Working on frameworks (and dev tooling in general) is such and interesting and subtle game. If we don't built-in enough abstractions / flex points people won't be able to do their job. But too much flexibility can make the tool cumbersome to use for _typical_ situations. 1/3

🚀 Meet Angular v19 ‣ Incremental hydration ‣ Server route config ‣ linkedSignal, resource, renderEffect ‣ Auto CSP ‣ Unused import reporting ‣ Standalone by default ‣ Enhanced theming ‣ Time picker ‣ 2D drag & drop ‣ Many codemods to modernize your code Much more! blog.angular.dev/meet-angular...

Angular v19 has so much great stuff: important improvements and updates, essential new building block and some ground-breaking tech. Developer event starting in... like 1 minute, will cover it all: www.youtube.com/watch?v=JvkX...

Less than 24 hours away 🚀 www.youtube.com/watch?v=JvkX...

All modern JS frameworks run on the same idea: model driven UI (data is the source of truth) + declarative model to the UI mapping ("templates"). Simple, powerful and consequential. But I like pushing those simple stories to the "extreme" and "see what breaks". There are 2 places with cracks. 1/3

Angular v19 ships with the two new reactive APIs: linkedSignal and resource. On the surface those might seem like unrelated APIs. The truth is that both come from the same line of thinking: derive state without effects. Both linkedSignal and resource can be seen as specialized "computed".

Many of the design decisions in Angular have a very simple "backing story". One or two fundamental thoughts. But somehow those cornerstone thoughts are lost, or simply untold, when foundational ideas are translated into APIs and make into a release. 🧵

@devagr.bsky.social digging deeper into github.com/devagrawal09... and trying to wrap my head around the practical implications of "reducing events to state" (state = f(events)) approach vs. collocating mutation methods with a signal. 1/n

Tool preferences is something that was on my mind quite a bit lately. Some heated A vs. B tech debates are really about tools philosophy. Ex.: small, focused and composable vs. do it all / integrated. It is not like is "better" than the other. All depends on the current needs. And ones preferences

I must say that I'm pretty happy about the direction of the Observable spec (github.com/WICG/observa...) and its focus on processing events. Thnx @domfarolino.com for taking time to chat about it today. And looking forward to collaborating more, especially around linking / reducing events to state.

I'm extremely proud of this release. There are so many important things that made it to v19!

Would love to connect with people that are / were using cyclejs extensively. Trying to understand what works and what doesn't -on the high architectural level. Who would be a good person to talk to?