Live data from Hacker News

Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc

twitter.com

751–754 of 754 posts

Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc

#751

Earlier quoted context omitted.

If anything LLMs should use something higher level because it compresses the context and makes programming closer to natural language they are trained on. Forcing LLMs to do a shitty job of what a compiler can do deterministically is not a good approach IMO.

Low level was the wrong term for me to pick there. I was meaning more along the lines of "purpose built". I.e. I could see a language, potentially still an abstraction requiring a compiler, that isn't meant to be particularly meaningful or inspectable by humans. For LLMs your right, conciseness would be important and that would likely mean it would be compiled.

you're both under and over estimating this technology I think, we are further away from SWE becoming a niche job than you think, but also LLMs really are less impacted by programming language than you think, this is a very pre-2010s approach to NLP, it really matters quite little to a language model what language the code is in, you could have it write it in Python using exclusively Chinese logographs for names, and exclusively French transliterated into Mayan script for comments and it might barely perform worse than if you asked it to do something normal, but that also goes in the other direction, trying to design a language that's "friendly" to LLMs will likely not do much good either. The reality is there's a massive amount of data on existing languages and they are good enough for LLM usage.

I think if changes will happen in this direction it will be around formal verification, it's more difficult to trust LLM generated code if you aren't completely brainroted on press releases, and traditionally formal verification was seen as more effort than it's worth, but a tool that's great that generating insane amounts of text is quite well suited to formally verifying code, and assuming you can figure out how to make the specification readable to people, you just don't (in theory) need to ever look at the code or the proof, even if it might be helpful to anyways in practice. I'm quite excited the future of software might be fully unhackable software being the standard, with hacking becoming something that's talked about as a brief criminal fad in the beginning of the 21st century, like how you might hear about coin clipping from before fiat currency.

Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc

#752

Earlier quoted context omitted.

which is a good thing. C++'s RAII is magic-sauce that does a lot for you when you can simply use `defer` in zig. A constructor is just a function call. A destructor is just a function call.

It's not a good thing. The reasoning is extremely simple and I don't understand how can anyone oppose it: there are some operations that you don't want to forget BY DEFAULT. If I open a file, eventually I want to close it. If I allocate some memory, eventually I want to deallocate it. Any programming language design that intentionally puts the onus BY DEFAULT on the user to *not forget to manually do something* is ho…

One of the core design principles of zig is no implied behavior.

Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc

#753

Earlier quoted context omitted.

no, in zig it's never unexpected, because if you're freeing memory the freesite is known, it's a function call.

Right; because in zig the default behaviour is to leak memory. Rust adds an invisible free() call. Leaking is something you have to do explicitly. I understand zig's philosophy here. But I prefer rust's default behaviour.

Zig fails unit tests if there's a memory leak in those tests.

Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc

#754
post #75

Very impressive that they could do this so quickly because I have been on a similar project (porting TypeScript to Rust) for 5 months. But I guess I don't have access to Mythos and unlimited tokens. I'm also close to 100% pass rate. 99.6% at the time of writing. https://tsz.dev Rust is perfect for writing all of code using LLM. It's strict type system makes is less likely to make very dumb mistakes that other languag…

Same but for multi-threaded Postgres[0]. 96% pg regression tests pass after 1 month and 823K LOC. 8 Codex accounts at $200/mo is what i could use up with no Mythos I've also seen the benefits of Rust for this too. And making the bet that my pg experience will help me make good design choices around many of the things people have been having trouble with in pg for a long time[1]. Excited to see AI make it more possibl…

[flagged]
Post reply on HN