One more reason to use @pnpm.io and @npmx.dev:
trust policy downgrade becomes visible and preventable
Posts by citriqa (extra tart edition)
now that everything is going to get owned maybe i should pick up my idea of the per-process vm for linux again
isn't facebook working on fixing this with react-strict-dom? once the web isn't a second class target, libraries will be built to account for it
right now sprites.dev appears to be the only cloud offering that can actually fully scale vertically; to zero with rapid unsuspend, and in terms of instance resources too
some thoughts on saas companies and coding agents
1) i think that the threat of claude code and codex to a lot of saas companies is that it commoditizes their software expertise
"To achieve this, we implemented a WebAssembly interpreter inside the transformer weights."
sentences with terrifying aura
Image from X
sent this to the team today
everything great comes from being able to delay gratification for as long as possible
and it feels like we're collectively losing our ability to do that
Only for team/enterprise for now, but it looks like Anthropic has more or less just killed all of the AI code review wrapper startups. This seems to be super in-depth (expensive!) and supposedly less than 1% of reviews are flagged incorrect. Excited to see if pro/max gets this.
So two psychologists walk into the speculative agentic coding design space bar and......have a lot of ideas for developer learning!
@mcmullarkey.bsky.social has written a new Skill that we've layered into Learning-Opportunities: Orient! β¨β¨
github.com/DrCatHicks/l...
having used claude extensively for the past couple of months, i think there is still a lot of value to understanding your code and steering it intentionally. the amount of incidental complexity claude accumulates otherwise (which mostly results in bugs that it can't ever fix reliably) is staggering.
The problem is that in legal work, the only validator is the judge and you only get one run at it
stereOS: a Linux based operating system hardened and purpose built for AI agents
"A full NixOS system that you boot and then kick off agent sandboxes inside with gVisor + /nix/store namespace mounting. Each agent gets their own kernel and the /nix/store is read only by nature.
i rarely use subagents because i can't see their thinking and can't monitor if they're on the right track. :(
Itβs no mistake that Claude Code is beating everyone else
AI safety = stable & well functioning AI
Skimping on safety makes your product worse
www.theverge.com/ai-artificia...
what might change is the "better is worse" rule for software, because writing good code will not be the bottleneck anymore to creating software
bad software has always been fast to write, good software took a lot longer. LLMs accelerate both dramatically but the dichotomy still holds
it's beginning:
github.com/tldraw/tldra...
does this actually save on usage? i think there's a reason this option is hidden, and that's the cache busting a model switch causes
i'm thinking i should teach the machine brain to do 2D programming
@theo on twitter: Gen Z is right. File systems are bad design. We've stockholm syndrome'd ourselves into thinking otherwise.
he's based now. the operating system of the future will use a capability restricted database instead of a traditional file system
@dhh: What a perfect illustration of the type brain in its most rabid form. Catastrophizing the use of dynamic typing to the point of death. Fascinating state of mind.
the absence of type safety is responsible for loss of life and livelihood in the same way as absence of memory safety or thread safety. if you are writing serious software, it is not a matter of taste.
whenever i hit ")" and visual studio just advances the cursor past the existing ")" that's one position ahead of where i was, instead of inserting an additional ")" as i intended, i feel undermined, i feel indignant, i feel i have been spat on
I guess StackOverflow is done.
Thatβs a little discouraging, but okay
...and language is a poor medium for designing easing curves and aesthetic feelings. I always need to touch the code, and it's often faster to CSS than prompt.
FE requires constant human-in-the-loop checks so even if you have a dozen agents working, I am the bottleneck. Scale isn't that helpful.
Out-of-order HTML patching, another proposal from TPAC, lets HTML be presented non-linearly, and a single file can update multiple parts of the page.
Would this feature be useful to you?
Been using this repo to iterate on API ideas for a concurrent compatible store for React. Still exploratory but excited that weβre very close to something that we can start trying out with existing data stores and start an iteration cycle based on what we learn.
react is going incremental? the react fir prototype
youtu.be/zyVRg2QR6LA?...