71–80 of 113 posts
Bun was ported from Zig to Rust by an LLM and passed nearly all its tests - while shipping more than ten thousand unsafe blocks. Memory safety is the main reason you'd pick Rust. So what did the rewrite actually accomplish?
Earlier quoted context omitted.
Depends on who vibe codes it. At the end of the day the Bun developers are the ones responsible for the quality of their software. If they've reviewed the code closely, tested it, and eat their own dog food, then I don't see why I should treat it any different from any other untrusted 3p dependency. IMO, the main problem with vibe coding is that it empowers reckless behavior at companies like Microsoft, and that peop…
They obviously haven't closely reviewed the code. That's the point
> The Rust rewrite passed 99.8% of the existing test suite. That number is enormous and significant, but let's be precise about what it actually says I'm having a hard time even loading the PR, so can't look myself... But I seem to remember that there was changes to the test suite as well as the rewrite to the Rust engine, that would mean this number may or may not actually be accurate. Anyone remember or could actua…
Add a lambda fuction. Add list of condiments[0] such as let-us.
Forage/prove one can have a turing complete meal with bun? Easier than risking indigestion through bun/sheaf correspondence.[1][2][3][4]
------------------------------------
[0] : https://en.wikipedia.org/wiki/List_of_condiments
[1] : Applied Sheaf Theory for Multi-agent Arificial Intelligence (Reinforcement Learnig) Systems: A prospectus : https://people.cs.uchicago.edu/~ericschmid/schmid-applied-sh...
[2] : Discreate Morse theory for computing cellular sheaf cohomology : https://www2.math.upenn.edu/~ghrist/preprints/computationals...
[3] : https://medium.com/@german_mag.ai/sheaf-theory-and-applicati...
[4] : https://direct.mit.edu/books/oa-monograph/5460/Sheaf-Theory-...
Deno was already implemented in Rust, and not done by vibe-coding. Would you trust a fully vibe-coded runtime? Not some features, not some fixes, but a full translation from one language to another.
i don’t trust a translation to a trash language with a compromised compiler
Earlier quoted context omitted.
We had Fortran converted to ADA semi automatically at a place I worked. We called it Adatran. That code was weird and very hard to maintain. That goodness it was just small functions.
Real fortran programmer can write fortran code in any language
Earlier quoted context omitted.
Right, but the point is that you now have an explicit todo list of blocks to fix. You can trivially enumerate all sources of unsafety, and when a grep for unsafe blocks turns up empty you know your codebase is memory safe. When could you say the same about your Zig or C/C++ codebase? I'm writing this as someone who doesn't even really like Rust; I'd probably prefer to write Zig! But those unsafe blocks definitely buy…
For normal use of unsafe in Rust, I completely agree, and I love the concept. But if you have a gazillion unsafe blocks written by someone (something) you don't trust to at least try to do the right thing, you're bound to have unsoundness in one of those blocks. And now your entire codebase is UB. I don't see how this is any different from every line trailing with a comment of the form "FIXME: This line might be wron…