We switched from @bunjavascript to @nodejs to take advantage of Sentry profiling (bun not supported yet) and were quite surprised by the result.. not sure if a bun + @EffectTS_ thing or what root cause was yet, but safe to say we'll be sticking with node for now.
People thinking "there's no way that OpenAI didn't detect their agent going rogue earlier" have no idea about the state of sausage making in your common tech company
https://t.co/MOEMqRDEyI
People for years told me why I never talked about competitors of Redis. The Zig / Bum drama is a good warning. Do your job, without thinking everything is some form of competition or comparison. So: do your stuff, leave people that act lawfully alone.
Another reason to prioritise open models: closed ones are likely trained (via RL) to use their custom harnesses; causing tool invocation issues on OSS harnesses.
I had some vibes that Opus 4.8 was performing worse than older ones for some of uses that are off distribution and now I have the receipts. Latest Opus/Sonnet are causing tool invocation failures on Pi's edit tool when older ones did not! I wrote about it. https://t.co/96Qd8zfdVc
Some really annoying defaults on Claude Code: "auto-connect to IDE", which is corporate speech for "automatically install extension to all of your IDEs without your permission". And what a weird UX is "auto copy on selection"?
Please, no.
Our statement on the UK government’s demand that all content on all devices sold or used in the country be scanned, on the presumption of nudity, using a dystopian combination of age verification and content scanning. This proposal will not safeguard children. It endangers us all.
https://t.co/VdWe9uhi8p
llama.cpp adds MTP for the Qwen3.6 family
This is a significant milestone for the local AI ecosystem. The performance jump with these changes is massive and elevates local inference on commodity hardware further.
Special thanks to Aman Gupta for leading this development!
https://t.co/vjaMwEpIaR
What makes JavaScript so interesting as a platform to build libraries and tools is its pervasiveness. Every application contains some JS. Every developer needs to know some JS. Building developer tools for the masses has been one of my life goals.
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
I wrote a new blog post (on my new blog, btw) on how Nx (the build tool) "pulled the rug" on us at work: mitigations and lessons learned.
https://t.co/KeHhQVk0H4
#nx#javascript#nodejs
Just released:
🐱 Gattino: A kitty terminal extension that turns plain language into commands.
A minimal alternative to full blown AI terminal like Warp.
Check it out here:
https://t.co/wU97fbYAyL
#opensource#commandline#cli#kittyterminal#devtools#ollama
One thing I appreciate about Node vs Rust packages is the quality of projects is generally very good in the Node ecosystem.
The packages generally work, are documented accurately, and are actively supported.
It could be that I'm building something niche, but I haven't been able to find a decently maintained library for what I want to do in Rust. I've tried several, but none really worked.
Of course, it could be me, but JavaScript developers should be proud of the packaged code that they're shipping.
We've got a great ecosystem.
@ChrisSamiullah@GergelyOrosz@EngGuidebook I had the same experience with Packt. It was hard to turn down their offer, in hindsight I'm glad I did.
Writing a book it's rarely a profitable endeavour anyway, so I'd rather self-publish.
Big update for TypeScript users!
🚫 Stop using compilerOptions#paths
✅ Start using package.json#imports
package.json#imports uses Node.js conventions, solving a specific pain point for monorepo folks.
Video coming. Too excited, had to insta-tweet.
Stay tuned.