RT @PushBased: ๐ธ ๐๐ถ๐๐๐๐ฏ ๐๐ผ๐ฝ๐ถ๐น๐ผ๐ ๐ท๐๐๐ ๐ฐ๐ต๐ฎ๐ป๐ด๐ฒ๐ฑ ๐ต๐ผ๐ ๐ถ๐ ๐ฐ๐ต๐ฎ๐ฟ๐ด๐ฒ๐ ๐ณ๐ผ๐ฟ ๐๐.
As of June 2026, @github is moving away from per-request billing and iโฆ
๐ ๐๐ง๐ ๐ฎ๐ฅ๐๐ซ ๐๐ ๐๐๐ฐ๐ฌ: ๐๐๐ฆ๐ฆ๐๐ซ๐๐ ๐ข๐ฌ ๐๐๐ฆ๐จ๐ฏ๐๐
After nearly 10 years, @angular officially removes built-in support for HammerJS.
With Angular 22, HammerModule is gone โ another step toward a leaner and more modular framework.
๐ What changes?
๐งน ๐๐๐ฆ๐จ๐ฏ๐๐ ๐๐ซ๐จ๐ฆ ๐๐จ๐ซ๐
HammerModule is no longer part of Angular.
๐งฉ ๐๐ซ๐ข๐ง๐ ๐๐จ๐ฎ๐ซ ๐๐ฐ๐ง ๐๐จ๐ฅ๐ฎ๐ญ๐ข๐จ๐ง
If your app relies on gesture handling, youโll need to integrate it yourself.
๐ก ๐๐ข๐ ๐ซ๐๐ญ๐ข๐จ๐ง ๐๐ข๐ฉ
You can copy the previous implementation into your own codebase if needed.
โ๏ธ ๐๐๐๐ง๐๐ซ ๐๐ง๐ ๐ฎ๐ฅ๐๐ซ ๐๐จ๐ซ๐
Angular continues reducing built-in dependencies and keeping the framework focused.
This follows a bigger principle:
keep the core minimal and let teams decide what they actually need. ๐ฅ
#Angular #WebDev #Frontend
๐ ๐๐ง๐ ๐ฎ๐ฅ๐๐ซ ๐๐: ๐๐๐ญ๐๐ก ๐ข๐ฌ ๐ง๐จ๐ฐ ๐ญ๐ก๐ ๐๐๐๐๐ฎ๐ฅ๐ญ ๐๐จ๐ซ ๐๐ญ๐ญ๐ฉ๐๐ฅ๐ข๐๐ง๐ญ
@angular is modernizing how HTTP requests work under the hood.
๐ What changes?
๐ ๐๐๐ญ๐๐ก ๐จ๐ฏ๐๐ซ ๐๐๐
The native fetch API becomes the default instead of XMLHttpRequest.
๐งน ๐๐๐ฌ๐ฌ ๐๐จ๐ง๐๐ข๐
withFetch() is no longer needed โ itโs the default now.
๐ ๐๐ฉ๐ญ-๐ข๐ง ๐๐จ๐ซ ๐๐๐ ๐๐๐ฒ
If you rely on XHR features like upload progress, you can switch back explicitly.
โ๏ธ ๐๐จ๐๐๐ซ๐ง ๐๐ซ๐จ๐ฐ๐ฌ๐๐ซ ๐๐ญ๐๐ง๐๐๐ซ๐๐ฌ
Better alignment with todayโs web platform APIs.
๐ก ๐๐ฆ๐ฉ๐จ๐ซ๐ญ๐๐ง๐ญ ๐๐จ๐ญ๐
Upload progress tracking still requires XHR โ so choose based on your use case.
Another example of Angular reducing boilerplate while aligning with the platform.
#Angular #WebDev #Frontend
๐ ๐๐ง๐ ๐ฎ๐ฅ๐๐ซ ๐๐.๐: ๐๐๐ฌ๐ญ ๐๐ซ๐ ๐ฎ๐ฆ๐๐ง๐ญ๐ฌ & ๐๐ฉ๐ซ๐๐๐ ๐๐ฅ๐๐ฆ๐๐ง๐ญ๐ฌ ๐ข๐ง ๐๐๐ฆ๐ฉ๐ฅ๐๐ญ๐๐ฌ
@angular templates are becoming much closer to real #JavaScript.
With Angular 21.2, you can now use rest arguments and spread elements directly inside template expressions.
๐ What changes?
โก ๐๐๐ญ๐ข๐ฏ๐ ๐๐ฉ๐ซ๐๐๐ ๐๐ฎ๐ฉ๐ฉ๐จ๐ซ๐ญ
Use spread syntax for arrays and objects directly in templates.
๐ง ๐๐ฅ๐๐๐ง๐๐ซ ๐ ๐ฎ๐ง๐๐ญ๐ข๐จ๐ง ๐๐๐ฅ๐ฅ๐ฌ
Pass arguments more naturally with spread patterns.
๐งน ๐๐๐ฌ๐ฌ ๐๐จ๐ฆ๐ฉ๐จ๐ง๐๐ง๐ญ ๐๐จ๐ข๐ฅ๐๐ซ๐ฉ๐ฅ๐๐ญ๐
No need for extra helper methods just to reshape arrays or objects.
โ๏ธ ๐๐๐ซ๐๐จ๐ซ๐ฆ๐๐ง๐๐-๐๐ฐ๐๐ซ๐
Angular integrates spread arguments into its existing pure function infrastructure to avoid unnecessary object recreation.
Templates keep getting smarter โ without sacrificing performance.
#Angular #TypeScript #Frontend
๐ ๐๐ ๐ฃ๐ผ๐๐ฒ๐ฟ๐ฒ๐ฑ ๐๐ป๐ด๐๐น๐ฎ๐ฟ ๐ง๐ผ๐๐ฟ โ ๐ป๐ด๐๐ผ๐ฑ๐ & ๐ป๐ด๐๐ฎ๐๐ผ โค๏ธ
The final two stops of the tour are behind us ๐โจ
Over the last two days, we had the chance to meet the #Angular community in Lodz (20.05.) and Katowice (21.05.) for evenings full of modern @angular, accessibility engineering, AI-native workflows, and amazing discussions โก๐ง
A huge thank you to the organizers of @NgLodz and #ngKato for the warm welcome and for building such incredible local communities โค๏ธ
And of course โ thank you to everyone who joined the meetups, attended the talks, asked thoughtful questions, and continued the conversations long after the sessions ended ๐๐
๐ค @AdrianRoOmanski presented:
๐ง๐ต๐ฒ ๐๐น๐๐ฒ๐ฝ๐ฟ๐ถ๐ป๐ ๐ผ๐ณ ๐๐ฐ๐ฐ๐ฒ๐๐๐ถ๐ฏ๐ถ๐น๐ถ๐๐: ๐ ๐๐ฒ๐ฒ๐ฝ ๐๐ถ๐๐ฒ ๐ถ๐ป๐๐ผ ๐๐ป๐ด๐๐น๐ฎ๐ฟ ๐๐ฟ๐ถ๐ฎ
๐ค @Michael_Hladky presented:
๐๐ฒ๐๐ฒ๐ฟ๐บ๐ถ๐ป๐ถ๐๐๐ถ๐ฐ ๐๐ ๐ช๐ผ๐ฟ๐ธ๐ณ๐น๐ผ๐๐ ๐ณ๐ผ๐ฟ ๐ฎ ๐๐ฎ๐ฟ๐ด๐ฒ-๐ฆ๐ฐ๐ฎ๐น๐ฒ ๐๐ผ๐ฑ๐ฒ ๐๐ฎ๐๐ฒ
Weโre incredibly grateful for all the conversations, feedback, and energy throughout the entire tour โค๏ธ๐
Here are some impressions from @NgLodz and #ngKato ๐ธ
#Angular #AI #Accessibility #Frontend #WebDevelopment #SoftwareEngineering #AngularCommunity
๐ Thanks to everyone who joined the ๐๐ป๐ด๐๐น๐ฎ๐ฟ ๐ฉ๐ถ๐ฒ๐ป๐ป๐ฎ ๐ ๐ ๐ฅ๐๐ฆ ๐ฉ๐ถ๐ฒ๐ป๐ป๐ฎ meetup yesterday!
Big thanks to:
๐ค Robert Maier-Silldorff @RmRobsen
๐ค Dominic Bachmann
๐ @Lean_Coders for hosting, drinks & pizza
Great talks, great discussions, great community ๐
๐ ๐๐ง๐ ๐ฎ๐ฅ๐๐ซ ๐๐.๐: ๐๐ง๐ฌ๐ญ๐๐ง๐๐๐จ๐ ๐ข๐ง ๐๐๐ฆ๐ฉ๐ฅ๐๐ญ๐๐ฌ
@angular templates keep getting closer to real TypeScript.
With support for the instanceof binary operator, you can now perform cleaner type checks directly inside your templates โ no workaround needed.
๐ What changes?
๐ง ๐๐๐ญ๐ข๐ฏ๐ ๐๐ง๐ฌ๐ญ๐๐ง๐๐๐จ๐ ๐๐ก๐๐๐ค๐ฌ
Use instanceof directly inside @if blocks.
๐ก๏ธ ๐๐๐ญ๐ญ๐๐ซ ๐๐ฒ๐ฉ๐ ๐๐๐ซ๐ซ๐จ๐ฐ๐ข๐ง๐
Angular understands the type and gives safer access inside the block.
๐งน ๐๐๐ฌ๐ฌ ๐๐จ๐ข๐ฅ๐๐ซ๐ฉ๐ฅ๐๐ญ๐
No need for helper methods just to perform runtime type checks.
โ๏ธ ๐๐จ๐ซ๐ ๐๐ฑ๐ฉ๐ซ๐๐ฌ๐ฌ๐ข๐ฏ๐ ๐๐๐ฆ๐ฉ๐ฅ๐๐ญ๐๐ฌ
Your template logic becomes clearer and closer to standard TS patterns.
Small feature โ but a very nice DX improvement.
#Angular #TypeScript #Frontend
๐ง ๐๐ถ๐๐ถ๐ป๐ด ๐ฌ๐ผ๐๐ฟ ๐๐ ๐๐ด๐ฒ๐ป๐ ๐ฎ โ๐ฆ๐ฒ๐ฐ๐ผ๐ป๐ฑ ๐๐ฟ๐ฎ๐ถ๐ปโ
๐ค AI agents can read code.
โก They can generate code.
๐ฅ But without architectural memory, they still make dangerous decisions.
๐คก A sarcastic PR comment from 2021.
๐ An outdated ADR.
๐ป A silently abandoned RFC discussed over beers years ago.
Thatโs often enough for an AI agent to confidently break your codebase.
In her latest article, ๐๐๐น๐ถ๐ฎ ๐ฅ๐ฎ๐ฝ๐ฐ๐๐๐ปฬ๐๐ธ๐ฎ explores a problem many teams are already running into with AI-assisted engineering:
โก๏ธ Context is scattered
โก๏ธ Tribal knowledge is undocumented
โก๏ธ LLMs lack architectural judgment
๐ซ The solution isnโt โbetter prompts.โ
๐ง Itโs building a structured memory layer for your AI agents.
๐ก ๐ง๐ต๐ฒ ๐ฎ๐ฟ๐๐ถ๐ฐ๐น๐ฒ ๐ฑ๐ถ๐๐ฒ๐ ๐ถ๐ป๐๐ผ:
โข Intent-driven wiki systems ๐
โข Rules vs. Guides vs. Context pages ๐๏ธ
โข Steering files & MCP workflows โ๏ธ
โข AI-safe SSR engineering patterns ๐ก๏ธ
โข How to stop agents from guessing architecture decisions ๐ฏ
๐งฉ ๐ข๐ป๐ฒ ๐ผ๐ณ ๐๐ต๐ฒ ๐บ๐ผ๐๐ ๐ถ๐ป๐๐ฒ๐ฟ๐ฒ๐๐๐ถ๐ป๐ด ๐ถ๐ฑ๐ฒ๐ฎ๐:
Instead of forcing agents to reconstruct project understanding from raw ADRs and transcripts every time, you create a synthesized โwiki layerโ optimized for execution and decision-making.
The result? ๐
โ More reliable AI-assisted development
โ Fewer hallucinated engineering decisions
โ Consistent architectural enforcement
โ Better onboarding for human teams too ๐
A very practical read for teams experimenting with AI agents in real production environments ๐
๐ https://t.co/wv9ZzH6rhW
#AIEngineering #SoftwareArchitecture #LLM
๐ ๐๐ง๐ ๐ฎ๐ฅ๐๐ซ ๐๐.๐: ๐๐ฎ๐ฅ๐ญ๐ข๐ฉ๐ฅ๐ ๐ฆ๐๐ญ๐๐ก๐ข๐ง๐ ๐๐๐ฌ๐๐ฌ ๐ข๐ง @๐ฌ๐ฐ๐ข๐ญ๐๐ก ๐๐ฅ๐จ๐๐ค
@angular templates keep getting cleaner and easier to maintain.
With Angular 21.2, you can now group multiple matching cases inside a single @๐ฌ๐ฐ๐ข๐ญ๐๐ก block โ making conditional rendering much simpler.
๐ What changes?
๐ง ๐๐ฎ๐ฅ๐ญ๐ข๐ฉ๐ฅ๐ ๐๐๐ฌ๐๐ฌ, ๐๐ง๐ ๐๐ฅ๐จ๐๐ค
Different values can now share the same rendering logic.
๐งน ๐๐๐ฌ๐ฌ ๐๐ฎ๐ฉ๐ฅ๐ข๐๐๐ญ๐๐ ๐๐๐ฆ๐ฉ๐ฅ๐๐ญ๐ ๐๐จ๐๐ or ngTemplateOutlet
No need to repeat the same UI for similar states or reaching for ngTemplateOutlet to re-use templates.
โก ๐๐ฅ๐๐๐ง๐๐ซ ๐๐๐ซ๐ฆ๐ข๐ฌ๐ฌ๐ข๐จ๐ง ๐๐จ๐ ๐ข๐
Perfect for role-based UIs like admin, editor, reviewer, and viewer flows.
โ๏ธ ๐๐๐ญ๐ญ๐๐ซ ๐๐๐๐๐๐๐ข๐ฅ๐ข๐ญ๐ฒ
Templates become easier to scan, understand, and maintain.
Small syntax improvement โ big everyday DX win.
#Angular #DX #Frontend
๐ ๐๐ง๐ ๐ฎ๐ฅ๐๐ซ ๐๐ ๐๐๐ฐ๐ฌ: ๐๐ฒ๐ฉ๐ ๐๐ก๐๐๐ค๐ข๐ง๐ ๐๐จ๐ซ ๐๐จ๐ฌ๐ญ ๐๐ข๐ง๐๐ข๐ง๐ ๐ฌ will be ๐๐๐๐๐ฎ๐ฅ๐ญ
@angular keeps pushing more problems from runtime โ compile time.
With Angular 22, type checking for host bindings will be enabled by default, helping developers catch issues earlier and ship more reliable applications.
๐ What changes?
๐ก๏ธ ๐๐ฒ๐ฉ๐ ๐๐๐๐๐ญ๐ฒ ๐๐ฒ ๐๐๐๐๐ฎ๐ฅ๐ญ
Host bindings are now checked automatically during compilation.
๐ ๐๐๐ซ๐ฅ๐ข๐๐ซ ๐๐ซ๐ซ๐จ๐ซ ๏ฟฝ๏ฟฝ๐๐ญ๐๐๐ญ๐ข๐จ๐ง
Issues that previously slipped into runtime can now be caught during build time.
๐ง ๐๐จ๐ซ๐ ๐๐๐ฅ๐ข๐๐๐ฅ๐ ๐๐จ๐๐
Templates and bindings behave more predictably.
๐ ๐๐๐ฌ๐ฌ ๐๐๐๐ฎ๐ ๐ ๐ข๐ง๐
Fewer โwhy is this not updating?โ moments in production.
This is part of Angularโs bigger direction:
less guessing, stronger compiler guarantees, and safer applications by default. ๐ฅ
#Angular #TypeScript #Frontend
๐ ๐๐ง๐ ๐ฎ๐ฅ๐๐ซ ๐๐ ๐๐๐ฐ๐ฌ: ๐๐จ๐ฆ๐ฆ๐๐ง๐ญ๐ฌ ๐ข๐ง ๐๐๐ฆ๐ฉ๐ฅ๐๐ญ๐๐ฌ
Sometimes the smallest features make the biggest difference in daily development.
@angular will support comments directly inside templates, making complex markup easier to understand and maintain.
๐ Whatโs new?
๐ฌ ๐๐ง๐ฅ๐ข๐ง๐ ๐๐จ๐ฆ๐ฆ๐๐ง๐ญ๐ฌ
Add comments exactly where the logic lives.
๐งพ ๐๐ฎ๐ฅ๐ญ๐ข๐ฅ๐ข๐ง๐ ๐๐ฎ๐ฉ๐ฉ๐จ๐ซ๐ญ
Use block comments for longer explanations and edge cases.
๐ง ๐๐๐ญ๐ญ๐๐ซ ๐๐๐๐๐๐๐ข๐ฅ๐ข๐ญ๐ฒ
Document tricky bindings directly in the template.
๐ค ๐๐๐ญ๐ญ๐๐ซ ๐๐๐๐ฆ ๐๐จ๐ฅ๐ฅ๐๐๐จ๐ซ๐๐ญ๐ข๐จ๐ง
Make intent clearer for teammates โ and your future self.
Small DX improvements like this remove friction every single day.
#Angular #DX #Frontend
Iโve written about a misconception I see everywhere right now:
Agentic UI is treated as a chat problem. Itโs not. ๐ง
Adding a sidebar with an LLM doesnโt create agency.
It creates a better text interface.
Real Agentic UI emerges when your system can:
โข reason over application state ๐งฉ
โข act through bounded tools ๐ง
โข adapt the interface ๐
โข recover from failure โป๏ธ
Thatโs not a feature you plug in.
Thatโs frontend architecture.
If youโre building AI into your product, start there.
๐ Read the full article: https://t.co/YzPLdqkmYS
๐๐ด๐ฒ๐ป๐๐ถ๐ฐ ๐จ๐ ๐ถ๐ ๐ก๐ข๐ง ๐ฎ ๐ฐ๐ต๐ฎ๐ ๐ฝ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ. ๐๐โ๐ ๐ฎ ๐ณ๐ฟ๐ผ๐ป๐๐ฒ๐ป๐ฑ ๐ฎ๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐๐๐ฟ๐ฒ ๐ฝ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ. ๐ง
Most teams still picture โagenticโ as a Copilot-style sidebar.
๐ง๐ต๐ฎ๐โ๐ ๐๐ต๐ฒ ๐๐ฟ๐ผ๐ป๐ด ๐ฎ๐ฏ๐๐๐ฟ๐ฎ๐ฐ๐๐ถ๐ผ๐ป โ
Real agency doesnโt come from a chat box. It emerges when your interface can:
- interpret goals ๐ฏ
- reason over application state ๐งฉ
- act through bounded tools ๐ง
- adapt the visible UI ๐
- recover from failure โป๏ธ
๐ง๐ต๐ฎ๐โ๐ ๐ป๐ผ๐ ๐ฎ ๐ณ๐ฒ๐ฎ๐๐๐ฟ๐ฒ. ๐ง๐ต๐ฎ๐โ๐ ๐ฎ๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐๐๐ฟ๐ฒ.
In our latest blog post, @Michael_Hladky breaks down:
- why chat-only approaches fail ๐ฅ
- what recent research actually shows ๐
- and why frontend teams own the hardest parts of Agentic UI ๐ฉโ๐ป๐จโ๐ป
If your roadmap starts with โletโs add a chat panel,โ youโre optimizing the wrong layer.
๐ Read the full article: https://t.co/5cbm15VLmt
#Frontend #AI #AgenticUI
๐ ๐๐ ๐ซ๐๐๐ฎ๐๐๐ ๐ ๐,๐๐๐+ ๐ฆ๐๐ง-๐๐๐ฒ ๐ฆ๐ข๐ ๐ซ๐๐ญ๐ข๐จ๐ง ๐๐ฒ ~๐๐%
Thatโs ~1770% efficiency improvement โก
Not by โjust using AIโ โ but by making AI reliable.
๐งฉ Structured context
โ๏ธ Orchestrated workflows
โ Continuous validation
If youโre wondering how this actually works in practice:
Weโve put the fundamentals into a hands-on workshop.
๐ ๐๐ ๐๐ฌ๐ฌ๐ข๐ฌ๐ญ๐๐ ๐๐๐ฏ๐๐ฅ๐จ๐ฉ๐ฆ๐๐ง๐ญ ๐ ๐จ๐ฎ๐ง๐๐๐ญ๐ข๐จ๐ง๏ฟฝ๏ฟฝ๏ฟฝ
๐ ๏ธ Build your own AI setup
๐ Create context for your project
๐ Turn AI into a reliable workflow
๐ Case study: https://t.co/QdNsVLjpg3
๐ Workshop: https://t.co/dQtwbfmKa4
#AI #SoftwareEngineering #DeveloperProductivity
๐ ๐๐ฎ๐ซ๐ง ๐๐ ๐๐จ๐๐ข๐ง๐ ๐๐ซ๐จ๐ฆ ๐ ๐ฎ๐๐ฌ๐ฌ๐ฐ๐จ๐ซ๐ค ๐ข๐ง๐ญ๐จ ๐ ๐ซ๐๐ฅ๐ข๐๐๐ฅ๐ ๐ฐ๐จ๐ซ๐ค๐๐ฅ๐จ๐ฐ
Most teams use AI.
Few use it systematically.
Thatโs where the real gains happen.
In our new workshop ๐๐-๐๐ฌ๐ฌ๐ข๐ฌ๐ญ๐๐ ๐๐๐ฏ๐๐ฅ๐จ๐ฉ๐ฆ๐๐ง๐ญ ๐ ๐จ๐ฎ๐ง๐๐๐ญ๐ข๐จ๐ง๐ฌ, youโll learn:
โ Prompt design that actually works
โ Context engineering for real projects
โ Validation strategies for reliable results
๐ก Youโll leave with a working AI setup for your own codebase.
(And if youโve seen our latest case study โ this is the foundation behind it ๐)
๐ https://t.co/dQtwbfmKa4
#AI #SoftwareEngineering #DeveloperProductivity
๐ฅ Talk throwback: @ManfredSteyer at #AngularVienna
๐๐ ๐๐ง๐ญ๐ข๐ ๐๐ ๐ฐ๐ข๐ญ๐ก ๐๐ง๐ ๐ฎ๐ฅ๐๐ซ ๐ค
See how to bring AI assistants into Angular apps with dynamic UIs & real use cases.
๐ https://t.co/yWCRNPHHzj
#Angular#AngularVienna#AI