`auto&&` has been standard syntax in C++ for going on 15 years now and has a very clear, irreplaceable meaning - a type-deduced forward reference - to any remotely competent developer.
1,795 karma · joined September 27, 2023
`auto&&` has been standard syntax in C++ for going on 15 years now and has a very clear, irreplaceable meaning - a type-deduced forward reference - to any remotely competent developer.
Can you point to an equal number of issue tracker tickets showing novel bugs or regressions in the canary build?
So if I use Zig, I need to do all of that perfectly from day one and I don't get any help from static analysis to do it. Or else I've poisoned my whole program in scary ways and will require a total refactor where I still won't have any help and once again can't make a single mistake.
So depending on how heavily agents are used on what tasks, it's entirely possible that you get worse work for more cost.
Incredible display of bad faith discussion. You should be ashamed.
And I'm not sure how you're responding to my comment. The parent said "this is a marketing stunt" derogatorily, as if it's slop that doesn't work. This is already the canary build, it's more stable than the current stable, and is actively in production products in wide use.
The parent is objectively wrong, whether or not I personally use Bun.
If Bun can't get it right starting in 2026 with all of Zig's tooling and someone who worked on the language, what hope does my random team have?
Especially when we could, instead, use Rust. With a larger community to boot.
EDIT: Oh, look, blog post on the front page now.
https://bun.com/blog/bun-in-rust
> Bun v1.3.14 was the last version of Bun written in Zig. Bun v1.4.0 will be the first version of Bun written in Rust. It's available in canary now.
So, yes, it seems it was definitely more than a "marketing stunt" and it's broadly available and slated to be the production release soon.
I use it primarily as a replacement for tmux to do terminal stuff, not use agents. It's awesome. It worked out of the box, has actually good, working mouse support, quickly ships fixes, and the defaults are sane with obvious behaviors represented in an intuitive TUI.
Because, otherwise, they would need to run those drives for years and years with reasonable cycling and read/write pressure to report accurate numbers based on real world failure rates in real conditions.
A machine that presses a keyboard switch 500 times a second for several days straight is obviously not indicative of someone actually using the keyboard. But it'll get the "absolutely beat the snot out of it" number, which is usually good enough for marketing.
Can we please stop the incessant belly-aching over problems that don't exist. I have to question if you even use these tools?
You already use the first, the second you should be using and has existed for years - it's a jest-compatible runner integrated to Vite.
Rolldown is a part of Vite already (since version 8, alongside other implementing tools like lightnincss).
The ox* suite are native replacements for eslint and prettier. The latter has existed for years. Both of them aim to be drop-in compatible soon.
This is a boring stack.
FWIR, prior to the purchase by Vercel (or was it Cloud flare?), Vite+ was going to be a convenient, no fuss, low movement way set up projects that they sold to businesses for funding.
The word incel, on the other hand, describes men who are disgustingly behaved and as a result are unable to have romantic relationships.
These are not, in any way, the same thing. This is NOT an example of horseshoe theory.