Ferdinand Malcher / Bluesky @fmalcher.de

Angular 19 ist da! 🎉 Mit der neuen Version bringt #Angular viele spannende Features, die uns das Leben erleichtern. 😻 Standalone Components als default, Resource API, Linked Signals & mehr – wir haben alles für euch im Thread + im Blog zusammengefasst! angular-buch.com/blog/2024-11-a…

🚀 Code Snippet of the Day: Connect #Angular Reactive Forms with Signals for two-way synchronization! Used functions: ⭐️ linkedSignal() ⭐️ toSignal() ⭐️ effect()

📢 New in Angular 19: Linked Signals = writable + computed state, all in sync! Check out our latest article with interactive examples to get started with this new experimental feature in v19.0.0-rc.0! Blogpost: angular.schule/blog/2024-11-l… 1/3

🔥 Neu in Angular 19: Die Resource API! Daten laden, neu laden & Status-Updates – alles mit der experimentellen Schnittstelle auf Basis von Signals. ⭐️ resource ⭐️ rxResource ⭐️Signals Bist du bereit, deinen Code zu vereinfachen?🤩 Details im Blog: angular-buch.com/blog/2024-10-r… 1/3

I just stumbled upon this image I took with these four fine gentlemen at a @GoogleDevExpert summit in Berlin. @samvloeberghs @christianliebel @webdave_de @fmalcher01

Viele neue Features in #Angular! ⚡️😍 📷 Wir migrieren das Beispielprojekt aus dem Buch und stellen die neuesten Konzepte praktisch vor: 🗽 Standalone Components ⚙️ Control Flow 🚦 Signals 🔁 input() und output() ⏱️ Router Input Bindings 💉 inject() … ➡️angular-buch.com/blog/2024-05-m…

I've just signed this and so should you! #PWA #Apple letter.open-web-advocacy.org

@Jean__Meche Looks like it's 500 MB and the value expressed here is Kibibytes 😄

This is odly specific 🤔

@maartentibau @angular And it has the new Angular logo and color 😇 and Standalone Components and ESBuild and Control Flow, haha

Jayyy... angularlogos.com now running on @angular 17!!!! All credits go to @fmalcher01 who did all the work 🙏😎

NgRx v17 is out! NgRx Signals, Operators, Performance Improvements, Workshops, and more! dev.to/ngrx/announcin…

Neu im Blog: Server-Side Rendering mit Angular 17! Mit 🅰️ #Angular 17 wurde der Build für SSR und Pre-Rendering grundlegend überarbeitet. Wir helfen euch beim Update und zeigen euch anhand unseres Beispielprojekts die Unterschiede! 👷‍♂️🔧 angular-buch.com/blog/2023-11-s…

Schön, dass ihr dabei wart! Diese motivierten EntwicklerInnen haben unseren Online-Workshop mit @fmalcher01 erfolgreich gemeistert. Jetzt seid ihr bestens gerüstet für eure zukünftigen Projekte! Viel Erfolg mit 🅰️#Angular, RxJs und TypeScript! 🚀🚀

@eugeniyoz @synalx @mgechev And just because the concept is stable doesn't mean at all it's finished and not "work in progress" anymore.

@eugeniyoz @synalx @mgechev The current signals implementation (the signal itself) is stable. Everything around it is not, which includes signal-based components and the whole Change Detection story as well as the patterns and habits that have to evolve over time.

Hey @synalx and @mgechev here is a serious and honest question for you, and I would like to get an honest answer: are Angular Signals supposed to be “change detection reactivity primitive” or “reactivity primitive”? right now there are multiple movements related to Angular Signals, and looks like some of them might be “off the rails” - you are tuning signals to better serve the needs of Change Detection, although initially they were presented as a “reactivity primitive” in Angular. So it turns out that right now it is safer to use observable-based application/component state management and ONLY use signals in the templates (and convert all the observables into signals when you need them in the template). What is the point of having a “customizable” equality check fn, if Angular pollutes the console if that fn is not equal to Object.is()? It really looks like some silly joke. If signals were a “reactivity primitive”, we would be able to use layers and layers of derived signals, and on every layer, we would be able to freely declare our customized equality check functions. Right now it's not the case, so all the “Signal Store” solutions/libraries look “betrayed” - they still naively think that Angular Signals are general reactivity primitive in Angular, while in fact signals are “tuned” to serve the Change Detection in the templates, not to be composed in layers and layers of the real reactivity.

@maartentibau @angular Haha, I had the same thought when we rebranded the @angular_schule page and I thought of all these logos … I will be there to review the PRs, no worries :joy:

With the new @angular logo being revealed A LOT of logos will need to be updated I guess… gonna be a busy time on the angularlogos.com repo! 🤩🤩

Today, we are excited to announce Angular.dev – the future home for Angular developers. goo.gle/angular-dot-dev

🅰️ Angular hat ein neues Logo – wir auch! Wir sind glücklich über die Angular Renaissance. Das neue Logo und die frischen Farben greifen wir deshalb jetzt auch in unserem Logo und unserer Webpräsenz auf! 😍 angular.schule/blog/2023-11-n…

🅰️ #Angular 17 ist (bald) da! 🎉 Die News im Blog: 🅰️ angular.dev neues Logo & Docs – Angulars Renaissance ⚡️ Signals stable 🌊 Neuer Control Flow: if, for, switch 👀 Deferrable Views mit defer 🛣 Routing mit View Transition 👷 ESBuild stable angular-buch.com/blog/2023-11-a…

@TlayudaRuda @digitalix @angular The complete contrary! 😇

Is @angular changing their logo? or is there something else going on here?