Pawel Kozlowski

@pkozlowski.bsky.social

Open source, Angular.

After using AI (chats / coding) for a while I would really like to invest into startups seriously working on the brain <-> computer interface. The distance between a thought and a result is still too wide. Typing and reading are now substential bottleneck for some of the work I'm doing.

Iterating on a "visiting card" with Gemini (changed the place recently so lots of friends / contractors / etc that need my new address). Kind of insane what you can do in very few steps... I like this last concept - going with it unless you all think is terrible or ... have better ideas!

Bild

Spent the last 4 months looking into LLM codegen quality and techniques of improving it for the new APIs (not in the training set). 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!

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!

Dominic Gannaway@trueadm.dev · 11mo ago

The team behind RippleJS has heard the feedback around the $ prefixed reactivity and we agree – the design wasn't quite there. So we've proposed an alternative. github.com/trueadm/ripp...

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?

Angular Connect@angularconnect.com · last yr.

We’re beyond thrilled to announce that the @angular.dev Core Team is joining us LIVE on stage at #AngularConnect! 🚀 Huge thanks for your incredible support. We’re honored to have you with us! 🙏 ❤️

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....

Ori Livni@orisomething.bsky.social · 2y ago

As I said in the other site: 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 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...

Modern Angular

Discover the new features and techniques of the most modern versions of Angular.</b> The powerful Angular framework is ever-evolving, with each new iteration bringing amazing new modern features. Mod...

manning.com

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...

Meet Angular v19

In the past two years we doubled down on our investment in developer experience and performance — in every single release we’ve been…

blog.angular.dev

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. 🧵