Because it will give you an answer instantly? There are plenty of other things you can bring to forums - news, projects, etc.
I mean... It legit can though. You may hate AI for coding but I don't see why you wouldn't use it for questions like this. Do you not think it could answer this question?
You know you can just ask AI trivial questions like this? This is well within its capabilities.
Maybe you want your wedding website to look different to other people's? You really want to believe AI is useless don't you...
(I mean it would be nice if it was so I get to keep my job but I'm not going to lie to myself.)
Because a vibecoded app is going to be a ripoff of its training data anyway. LLMs can’t produce creative or novel works
Dude it's 2026 not 2024. I know things are changing rapidly but that has been very obviously not true for at least 6 months. You need to spend a little dough and try out the latest models - I would recommend Argon because it seems to be as good as Astra and Opus 5.5 but is cheaper. Have a go at vibe coding something. Make architectural decisions but then let it cook. You're going to be shocked.
cross requires Docker which is a really awkward dependency, especially on Windows and Mac, or if you're already in Docker, e.g. in CI or a dev container.
Plus it's quite slow. Cargo zigbuild was a much nicer solution when I finally resorted to it. Zig is easy to install, even on Debian - just download and untar.
Why would you not reuse event pages for the next event?
How many times are you getting married? 😄
I’d expect that the code would be almost exactly the same as other code that already exists, in which case, why not use that code?
Uhm, because it's not the same? Why would I vibe code an app that's almost exactly the same as an existing one?
aws-lc-rs is probably the most popular but also quite annoying because it uses C, so cross-compiling is a bit of a pain. I only managed to do it thanks to cargo zigbuild which is amazing. (And kind of embarrassing that Rust has to use Zig to get a nice cross-compiling UX, but hey it works.)
The other one is ring, which I'm not really sure the status of but I recall they had some super weird versioning policies that weren't very popular.
I'm surprised they still got so many responses now that SO is dead.
His point could be valid, if C was working fine and Rust didn't fix it. But C isn't working fine and Rust is the first actual solution we've ever had.
He's just an old man saying we can't have cars on the road because they'll scare the horses.
Ok after reading the article this is bullshit. It's only because they are counting JavaScript and Typescript separately.
Great accomplishment. I think we all knew it must happen like this but it's great to see real world results.
I think this is probably actually the most useful part of the post:
Increasing productivity: Safe Coding improves code correctness and developer productivity by shifting bug finding further left, before the code is even checked in. We see this shift showing up in important metrics such as rollback rates (emergency code revert due to an unanticipated bug). The Android team has observed that the rollback rate of Rust changes is less than half that of C++.
I think anyone writing Rust knows this but it's quite hard to convince non-Rust developers that you will write fewer bugs in general (not just memory safety bugs) with Rust than with C++. It's great to have a solid number to point to.
I'm not sure what you're trying to say. Why would you announce news to AI?