Replying to @the_versecafe
Maybe, but I think for this to be useful we would need to rewrite the standard entirely. Most compilers already offer diagnostics for compilation, syntax, even formatting. I don’t see how code actions could be useful for agents. Maybe refactor tools could save a few steps? What else is left? Maybe cleaner “grep-like” and query features, which is not in the current protocol spec (in any useful way for agents at least).
One advantage of LSPs is that they are usually built to recover from incomplete or imperfect code so you can have full code diagnostics at once even when part of it is broken, not only at the first breaking point as compilers usually do, but that’s more of a common practice than a rule.
I’m building most of these directly on Silk’s compiler, and I have the LSP cause I’m vintage 🙃
I've been working on and off on a custom harness app for myself since I published effect-harness.
Claude's new Projects workflow works really well for me, but I needed something that could work across multiple accounts and providers, with support for custom environments like local machines, Hetzner VMs, and so on.
Building it has been a lot of fun. Making your own AI tools is just the coolest thing.
It's still missing some features, so I'm not ready to make the jump yet, but I'm really excited to start using it for real.
I love LSPs, but they're kinda dead.
Silk will still ship one. I've always been a sucker for a good LSP, but I'm doing it more as a tribute to past Julia's dreams than because current Julia needs it in her workflow.
Take away the features designed to help humans type code, and there isn't much left. Even what's left could probably be handled in much better, more useful ways.
I'd love to be proven wrong on this one though.
J�lia retweeted
Software is having its Industrial Revolution and it’s changing what matters in software frameworks. Today’s frameworks were designed for the crafty carpenter, tomorrow’s are designed for mass manufacturing processes where rigor > conciseness.
Take foldkit vs react/solid, for example. You can argue that foldkit is more verbose or complicated for some use cases compared to the traditional alternatives, but everything doable in react/solid is also doable in foldkit. Everything doable in foldkit is not (or at least not easily or consistently) doable in react/solid because they lack the rigor of command+event state machines with story & scene testing. Getting that back isn’t easy and is a substantial loss for agentic coding.
Before AI, there was the valid argument of picking what humans like best. Humans kinda suck at programming because we are constrained by our skills, taste and (lack of) discipline, so frameworks that worked in this era catered to the lowest common denominator of mass market human developers. While I agree that react/solid are powerful in the hands of humans, that simply doesn’t matter anymore.
What’s best for humans does not necessarily translate to what’s best for agents. Some tasks may indeed be “a bit harder” with foldkit in human terms, but AI is capable of solving all of them in a few minutes, so who cares. Instead of bike-shedding philosophy and taste, just choose the more rigorous (and scalable) option. It costs you nothing and gains you everything.
Effect is another example of this. With AI, now everyone of all skill levels can use advanced programming techniques that are objectively safer and more scalable, but were out of reach for many human programmers. Or didn’t appeal to the stubborn tastes of a particular person.
With humans now out of the way of technology adoption - I think it’s obvious that the following techniques are going to become way more commonplace:
1. State Machines
2. Functional programming
3. Declarative infrastructure
4. Test Driven Development
5. Domain Driven Design
6. Actor Systems
7. Rigorous API schemas
8. Type Safety and Formal Verification
9. Disciplined Operations (monitoring, on-call)
Alchemy is designed to bring these techniques together into a seamless experience for building and deploying applications of massive scale. It is the “rails” and “parts” of the ai software assembly line.
Replying to @samgoodwin89
And I'd go a bit further, what's best when humans write isn't necessarily best when humans check what agents wrote.
Replying to @agaledesma
quando minha esposa não fica brava comigo por algo que ela geralmente ficaria e eu acho q é pq ela desistiu de mim 😭
Love when AI picks up something I say and never forget it
Me: Yea, gray looks nice
27 sessions later: Julia loves gray make everything gray, are you sure you don't want it gray? Violets are blue, but you said you like gray, do you prefer
A: gray (recommended)
B: grey
Replying to @pincehighdie
as a lesbian, not really my cup of tea, but yea, objectively hot
Replying to @EgeMustafaCelik
I’m doing exactly that :).. im a long time fan of taffy
Replying to @just_be_dev
not as cool tho
maybe it will be your first Silk project? 👀
Replying to @just_be_dev
HAHAHAHA I was going for something simpler, like Silk GPUI..but who knows 🤷♀️
Porting libraries to Silk has been an amazing thing for stabilizing the language. In the last few days I ported
- QuickJs (JS engine)
- Google read-font and font-types (font parsing)
- Harfrust (font shaping)
- Metal bindings
- Flexbox + Block layout engine (this one is not a port, it's written from spec)
(btw, are you noticing a theme? 👀)
All resulted in many bug fixes and closing essential feature gaps in the compiler, and huge runtime and compile time performance improvement.
All of that without having to pause what was already on Silk's roadmap.
It's insane that AI can do that in a language it never saw.
3 years ago I implemented Flexbox in Zig, I was so proud of it, it took me weeks.
Silk first commit was 86 days ago, less than 3 months.
Don't get me wrong, it's been a shit ton of work, but still, 3 months for what used to take literally years.
Silk compiler is fully self hosted. Flexbox was an overnight spike. This is so crazy.
Astra has a serious problem of having zero respect for my github actions limits. One shot project, I didn't even see the result yet, and each run already takes 1h30m








