Just a heads up that you should never be rendering 10,000 lines of anything, especially if all the lines are the same height, as in code.
List virtualisation is a very old and simple technique.
You can experiment with the below at https://t.co/Zm4IRrfh9j
@PushBased@Michael_Hladky does this migration guide steps works with legacy? like doesnt have CD Onpush using decorators Input and not standalone component?
or should i migrate my component to signals before i do this steps?
Soft-launching https://t.co/eZVklroKBW today
"THE marketplace for AI agent skills"
VISION: Empower non-technical users to leverage skills with Claude and other tools
MVP mode with skills I've created
As usual, thanks for the support! 🙏🙏🙏
Tried YOLO26 by @ultralytics and I'm really impressed!!!
I tested YOLO26 Object Detection on images, videos, and my webcam with a single Python code
It's fast, with really small-sized models! Biggest model for detection of YOLO26 is just 113mb 🤯
Runs smoothly on my average Mac!
Built this using one Python file 👇 (link in comments)
Claude Code web is awesome!
was able to add a feature to my website in 3mins. generation feels like the cli
@claudeai cooked on this one! love it!
steps
> connect your github account
> choose a repo
> prompt a feature
> cc auto-creates a branch
> create a pull request from cc
> merge in github
here's how it feels 👇 (video 3x)
@RyanCarniato In journalism, "right of reply" implies that benchmark participants should be given access to the code before publication of the results.
It builds trust.
Unfortunately, this is the dirty game that React plays.
When they do poor in public benchmarks, they downplay the validity of the benchmark and say that performance isn't really that important. Then, they turn around and make a big deal out of performance when they can engineer themselves as winner in their private benchmarks.
It has been this way since the very beginning.
Recall the very first DB Monster perf demo of React where they showed how React outperformed Angular.js. This was the demo that arguably caused the shift away from Angular.js and to React.
But what came out rather quietly later?
Once the benchmarks were publicly released and Angular.js developers had a chance to look at them, they discovered that the Angular.js implementation was very poorly implemented. When they fixed it, Angular.js outperformed React.
But by then it was too late. The inaccurate perf "news" had spread, and the hype had taken over.
Rinse and repeat.
AI Coding CLI + @coderabbitai 🔥🔥🔥
Code reviews in the terminal is now possible with CodeRabbit CLI
Squash bugs before pushing code before making a pull request
Got early access and it's really helpful in my daily coding workflow
See how it works 🧵👇
It’s a prototype and very much a work in progress
But yes, you can start experimenting with Signal forms with today’s pre-release 21.0.0-next.2
#Angular
Creating user interface elements for our AI-powered app just became easier
Reusable AI Elements in @aisdk just dropped! Built on @shadcn and open source
Components list and link to docs👇🧵