
@panda__css & OSS, frenchy freelancer https://nitter.gq/t.co/QSSMKiB9tG
Montpellier
Joined November 2020
- Tweets3.5K
- Following396
- Followers1.8K
- Likes17.4K
alex retweeted
This is either a hot-take or painfully obvious:
Telling your agents what you want >>>>>> telling your agents what to do
alex retweeted
Next week's release of @alchemy_run is gonna be a banger.
Got Rivet, Effect Cluster, Archil, Daytona, Modal and E2B all coming.
Rivet and Effect Cluster will be deployable anywhere, distributed as swappable layers:
alex retweeted
Your Harness. You Define It.
Meet Creator Mode in DeepSeek Harness.
Turn ideas into plugins that you can use, from a design workspace to a sandbox game or a 3D LLM visualizer.
What will you create?
alex 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.
alex retweeted
Content mappers in TS 7.1 are an absolute game changer
It’s plugins for TypeScript: a way to dynamically compute a static type signature for external file types (.vue, .md, etc) and integrate them directly into tsc compilation
TypeScript 7.1 Beta is now available! Now with a preview API, content mapper support, new features, and some great optimizations. Give it a try and give us some feedback! devblogs.microsoft.com/types…
alex retweeted
Introducing tsrs: a Rust port of the TypeScript compiler 🦀
We are not forking TypeScript!
◆ In close collaborating with the TypeScript team
◆ Up to 8x faster than TS 7.0 & ~70% less memory
◆ Runs in WASM, so it works in your browser & on Workers
◆ Soon part of the Oxc toolchain
npx tsrs
blog.cloudflare.com/typescri…
alex retweeted
Effect v4 is here.
One ecosystem. Zero dependencies.
The next chapter of Effect and the foundation for building reliable software and AI agents in TypeScript.
alex retweeted
nobody talking about the effect+alchemy+cloudflare combo to literally build f'n anything
why not?
alex retweeted
I am on the search for work trials!
I have compiled some projects covering tools, libraries, graphics, Rust and JavaScript.
If you have opportunities or leads, please get in contact!
kaleidawave-public-pages.val…
alex retweeted
We are entering a new phase with @EffectTS_ where "implement natively" is more powerful and less work than "integrate", for example over the past two weeks we removed dependencies on "pg"/"node-postgres" and "fast-check" both leading to more performant and less buggy code
alex retweeted
Plannotator 0.27.0 is out.
Code review is not dead yet.
- Calldiffs by @tanishqk is integrated as an optional lens
- Guides support custom instructions
- Tailscale remote reviews - thanks @nikuscs for the POC that kicked this off & @freak4pc for final encouragement
- Customize review panel: turn off viewed, git add, and disable lens for cleaner UI
Pi - BREAKING:
Pi plan mode has moved from `/plannotator` to `/plannotator-plan-mode` to avoid confusion
CI pipeline hardened.
alex retweeted
Effect v4 Release Candidate is here!
After months of beta releases, real-world usage, and community feedback, v4 is entering the final stretch before stable.
Try it, migrate, test your integrations, and tell us what still breaks before 4.0.
↓↓↓
effect.website/blog/releases…
alex retweeted
We finally brought @EffectTS_’s API reference docs to the Effect website, for both v3 and v4. Also comes with an improved search experience.
Just the first step we're taking to improve our documentation as we prepare for a v4 release candidate!
alex retweeted
Introducing celld: a self-hosted, distributed Durable Objects and Workers implementation
- celld = V8 + S3 + SQLite + LTX+ Tokio
- programmed with exactly the Cloudflare Workers/DO JavaScript APIs and config
- order of magnitude cheaper at scale
- writes are durable before they're acknowledged, RPO=0
- only depends on an S3 compatible bucket - no other infrastructure
- ~4 MB memory per cell instance overhead
- hibernated cells cost ~nothing, just their S3 storage
- open source, Apache 2 licensed
alex retweeted
Good news everyone! (cit.)
The rules you love (and hate) from the @EffectTS_ LSP are now available as custom, type-aware OXLint rules!
Bring Effect-aware diagnostics directly into your OXLint setup, learn more here: github.com/Effect-TS/tsgo#ls…
alex retweeted
We shipped a brand-new Effect website.
Take it for a spin, click everything, and let us know what you think.
Bugs, feedback, confusing bits, we want all of it ↓
effect.website
Framework authors, please take a look at tsgo’s content mapping RFC, which could potentially solve type-checking and linting for frameworks.
github.com/microsoft/typescr…


























