;-)
;-)
Many learnings from the process, with the key one being: LLMs "preffer" good API design.
Codegen fails? Your human devs would be likelly confused as well!
Many learnings from the process, with the key one being: LLMs "preffer" good API design.
Codegen fails? Your human devs would be likelly confused as well!
We did quite a bit of Angular syntax fine-tuning + using the tool to drive design of some new DSLs (with some the ideas very similar to RippleJS).
@devagr.bsky.social was also toying with it for SolidJS.
Interested?
We did quite a bit of Angular syntax fine-tuning + using the tool to drive design of some new DSLs (with some the ideas very similar to RippleJS).
@devagr.bsky.social was also toying with it for SolidJS.
Interested?
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.
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.
More seriously, the article does a great job of pointing out some friction points with signals. But IMO those are easier to live with when compared to friction points of alternatives.
More seriously, the article does a great job of pointing out some friction points with signals. But IMO those are easier to live with when compared to friction points of alternatives.
My main reasoning is that library-agnostic widgets need to compromise to fit into different frameworks and not making full advantage of the ecosystem.
Plus "generic" design is often harder, makes lib iterations slower etc.
My main reasoning is that library-agnostic widgets need to compromise to fit into different frameworks and not making full advantage of the ecosystem.
Plus "generic" design is often harder, makes lib iterations slower etc.
- 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!
github.com/trueadm/ripp...
- 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!
@what_the_stack
conference.
Arriving a few days earlier to explore Skopje was a great move - loving it here!
@what_the_stack
conference.
Arriving a few days earlier to explore Skopje was a great move - loving it here!
Don't miss your chance to see AI demos, get key updates from the Angular team, and have your questions answered live.
Tune in to see what's next:
🔗 youtube.com/live/uFdxw4S...
@angular.dev
code. They are _great_.
Totally should be part of the #Angular community, proudly wearing a #Angular T-shirt.
@angular.dev
code. They are _great_.
Totally should be part of the #Angular community, proudly wearing a #Angular T-shirt.
- APIs that are confusing for humans tend to be confusing for LLMs;
- APIs that are not flexible enough are more prone to hallucinations;
There are so many interesting techniques for using LLMs as user-study participants of sorts. A true LLM-driven design workflow.
- APIs that are confusing for humans tend to be confusing for LLMs;
- APIs that are not flexible enough are more prone to hallucinations;
There are so many interesting techniques for using LLMs as user-study participants of sorts. A true LLM-driven design workflow.
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
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
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?
Huge thanks for your incredible support. We’re honored to have you with us! 🙏 ❤️
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?
More info in developer.chrome.com/blog/perf-pa...
More info in developer.chrome.com/blog/perf-pa...
Blog post: vercel.com/blog/ai-sdk-5
Code sample: github.com/vercel/ai/tr...
Blog post: vercel.com/blog/ai-sdk-5
Code sample: github.com/vercel/ai/tr...
Especially @benlesh.bsky.social, @keithamus.social, @domenic.me, @jordan.har.band & more! 🙏
groups.google.com/a/chromium.o...
Especially @benlesh.bsky.social, @keithamus.social, @domenic.me, @jordan.har.band & more! 🙏
groups.google.com/a/chromium.o...
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...
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...
a) your initial motivations (dissatisfaction with the mainstream? something else?)
b) main ideas / initial story;
c) why it got abandoned / what was the insight leading to that decision.
a) your initial motivations (dissatisfaction with the mainstream? something else?)
b) main ideas / initial story;
c) why it got abandoned / what was the insight leading to that decision.
For one, after refactoring many apps, I see RxJS overused - where a simpler approach (signals, promises etc.) would work great.
Also, the upcoming Observables spec my change how we think about events processing and integration with signals.
For one, after refactoring many apps, I see RxJS overused - where a simpler approach (signals, promises etc.) would work great.
Also, the upcoming Observables spec my change how we think about events processing and integration with signals.
This requires adjustment in thinking but a reactive graph should describe relation between data and not a sequence of events.
This requires adjustment in thinking but a reactive graph should describe relation between data and not a sequence of events.
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....
A reminder, rendering performance doesn’t mean your app performance. Devs rarely use frameworks as intended, and these numbers we don’t really have. It’s more like you upper limit
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....
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!
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!
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...
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...