Why do people want this? Shipping constantly is how software breaks. You want tools that are good and stable, not constantly churning. I wish software developers would wake up to the idea that velocity is not a marker of quality.
Careful, focused work can easily sustain daily, or almost-daily, shipping. We've been doing it for decades without LLMs.
LLM-brain is pushing people into continuous by the hour shipping and it is absolutely unecessary and creating code at a rate that cannot possibly be kept up with in relation to quality, performance and security.
The main issue is side effects of effort/thinking it seems. It hallucinates at a much higher rate and skips research in a ton of edge cases even with effort of MAX and disabling adaptive thinking, even on 4.6. Ive said before, but using opus today feels like using sonnet from ~October timeframe. Its not anywhere near what opus 4.5 in January felt like, or even opus 4.6 on release (notably 4.6 on release _really_ over-researched even simple tasks and that behavior is almost entirely gone now even with max effort so they are definitely re-tuning these things on the fly and degrading the experience as a result).
EDIT: I also have a very high suspicion that the way they hydrate thinking is buggy and/or lossy (or maybe unintentionally lossy which leads to bugs). So many behaviors just make no sense at the level I have my setup tuned (I have everything set to "just charge me the most money to hopefully get the best results") and the fact that I havent changed anything while using it daily for months and months on end, but have been getting worse and worse results.
I used to be able to give it certain commands, and reliably count on it to do the right thing. Lately I give it identical commands and it just starts doing something idiotic, instead of the correct thing (that it did 50 times prior).
To an earlier poster's point, it's probably the model, not the harness, and I understand Anthropic has to make money someday (and they're not now) ... but I'd rather see a visible doubling of price than a secret halving of the capabilities (which seems to be their current plan).
That approach is enshitification.
I tried using bun for a project earlier this year and learned that you can't use testcontainers(works fine w/ Deno).
So the more direct question would be: How has Bun actually been since the acquisition?
From what I can tell they have been responding to users as fast as before, and improving the product as well as before.
Always appreciated nuance.
Then you could have been using Deno, like many of us, for years.
Been using Deno happily for many years now.
Did I miss anything?
Odd that aube is missing deno from their benchmarks though
They are not a runtime, but they do seem to be interested in wrapping a lot of tools with simple top-level commands