Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Zig → Rust porting guide

github.com

Post reply on HN
Print view View original

571–580 of 592 posts

Re: Zig → Rust porting guide

#571

Post by psychoslave »

tracker1 wrote: post #567
psychoslave wrote: post #555

Earlier quoted context omitted.

Isn't b it same to emit doubts that the resources required to find and access webpages or use a GPS is causing at scale the same ecological impact as everyone selling the world by the token. Though that might be wrong, of course, then doubts should be addressed with proper reasoning, not aggressive rejection which would be a call to run with a blind fold. Having people working together at some goal is not not going t…

I'm rejecting the pedantry of the premise altogether. YOU don't know the sources of energy used for the data centers in question... you aren't responsible and in a position to change anything... you are making statements to a negative assumption from the start and in such a hostile manner that any reasonable person would probably just ignore you. (I'm not always the most reasonable person) As for social structures in…

[dead]

Re: Zig → Rust porting guide

#573

Post by anymouse123456 »

randusername wrote: post #451
anymouse123456 wrote: post #90

This is a huge loss for the zig language and community. As a fan of the language, I hope it leads to some reflection on things that might need to change moving forward.

Nah, let the Zig foundation cook. Both their AI policy and their rejection of Bun's performance PR were level-headed and well-reasoned. And the link seems more like a proof-of-concept than anything else. It's true corporate sponsors are a big help with language development, but not at the expense of conceptual integrity.

I think I agree more with this take than where I started

Re: Zig → Rust porting guide

#574

Post by qurren »

saagarjha wrote: post #572
qurren wrote: post #569

Earlier quoted context omitted.

It only becomes your problem if you choose it to be your problem.

That is not how these things usually work.

Exactly. Usually is most people. You can choose to deviate.

You can delete your social media accounts and just keep working on what you want to, for one. Nobody is forcing you to use social media.

Re: Zig → Rust porting guide

#575

Post by Capricorn2481 »

baranul wrote: post #570
Capricorn2481 wrote: post #134

April 26th - Bun announces they used AI to fork Zig so they could make an optimization for a 4x improvement April 27th - Zig contributor mlugg clarifies why the specific optimizations Bun did were ill advised and wouldn't have been accepted in Zig, regardless of AI use [1] May 4 - Bun is looking into Rust as an alternative. This, to me, seems like total whiplash. Has anyone at Bun made a statement on why they're maki…

Zig is a pre 1.0 language, subject to many breaking changes and has thousands of (stranded) issues on its GitHub. It was always a risky proposition to use Zig, unless those persons were philosophically committed to help the language develop or die-hard fans. If not, them jumping to some other language, should not be so big of a surprise. They may come to the conclusion that Zig is incapable of delivering on its promi…

> They may come to the conclusion that Zig is incapable of delivering on its promises or is deficient at satisfying their requirements

Sure, but what you're suggesting is not related to the timeline I gave. They did not determine Zig was deficient in some way. They tried to get a cheap gain, and the gain breaks parts of Zig and they didn't even realize it, and it was worse than the gain already available in Zig. That seems less like they've made a pragmatic choice about speed and more like they are doing headline based development.

What you write makes it sound like there's a pragmatic process being followed that only you are privy to, and I'd like to know what it is. Zig may be inappropriate for Bun after all, but this makes it look like they don't understand what they are doing, and the agentic coding doesn't help.

Re: Zig → Rust porting guide

#576

Post by perching_aix »

qurren wrote: post #574
saagarjha wrote: post #572

Earlier quoted context omitted.

That is not how these things usually work.

Exactly. Usually is most people. You can choose to deviate. You can delete your social media accounts and just keep working on what you want to, for one. Nobody is forcing you to use social media.

I'm mostly on board with what you're saying, but under such an interpretation of "forcing", people are never truly forced into anything. That puts it in fundamental conflict with the very existence of the word, i.e. renders it meaningless.

That said, I did also walk away from most mainstream platforms already, so it's not like I disapprove of the message necessarily. I did find it regrettable that the calculus worked out that way though, and I don't find it reasonable to deny that there is / was a calculus. You do give up on things that are not just the assholes. I'd definitely classify that as a force.

But maybe I'm just missing that this was supposed to be inspirational rather than literal, and mistook your words. I don't know.

Re: Zig → Rust porting guide

#577

Post by bloppe »

Perz1val wrote: post #533
selectnull wrote: post #289

Why not rewrite claude-code in Rust? So, Anthropic acquires Bun team because claude-code uses Bun. They port Bun from Zig to Rust presumably because Rust "is better" (imagine big air quotes here). Again presumably, they want to make claude-code "better". Why make it so complicated? With all the power of LLMs they have, surely they can make claude-code the best possible by writting it in Rust directly.

Because afaik claude code is react rendered as TUI. They must really want react. I guess that happens to ones brain on too much ai

It mangles the render so often. Now I know why.

Re: Zig → Rust porting guide

#578

Post by hellohello2 »

Jarred wrote: post #319

I work on Bun and this is my branch This whole thread is an overreaction. 302 comments about code that does not work. We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely. I’m curious to see what a working version of this looks, what it feels like, how it performs and if/how hard it’d be to get it to pass Bun’s test suite and be maintainable. I’d like to be able to co…

You can view it as an overreaction, but also as a sign that your work is significant. It impressed some, and scared others. In any case, you made something interesting.

Re: Zig → Rust porting guide

#579

Post by baranul »

Capricorn2481 wrote: post #575
baranul wrote: post #570

Earlier quoted context omitted.

Zig is a pre 1.0 language, subject to many breaking changes and has thousands of (stranded) issues on its GitHub. It was always a risky proposition to use Zig, unless those persons were philosophically committed to help the language develop or die-hard fans. If not, them jumping to some other language, should not be so big of a surprise. They may come to the conclusion that Zig is incapable of delivering on its promi…

> They may come to the conclusion that Zig is incapable of delivering on its promises or is deficient at satisfying their requirements Sure, but what you're suggesting is not related to the timeline I gave. They did not determine Zig was deficient in some way. They tried to get a cheap gain, and the gain breaks parts of Zig and they didn't even realize it, and it was worse than the gain already available in Zig. That…

My description was pretty much on point. The authors of Bun appeared to have grown tired of Zig's "memory leaks, segfaults, and other stability issues". The statements (check their twitter/X) are not at all shocking, considering the over 3,000 stranded issues at Zig's GitHub repo.

Unless team Bun had some type of philosophical or financial allegiance to Zig, which they appear not to, it shouldn't be surprising that they jumped to some other language (Rust in this case).

> this makes it look like they don't understand what they are doing

Think it's more a matter of Zig not being able to deliver nor meet their requirements. That they may have got tired of Zig, so felt it was time to switch to something else, is their prerogative. Especially with having near unlimited tokens to blow.

Re: Zig → Rust porting guide

#580

Post by hn_throwaway_99 »

hellohello2 wrote: post #578
Jarred wrote: post #319

I work on Bun and this is my branch This whole thread is an overreaction. 302 comments about code that does not work. We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely. I’m curious to see what a working version of this looks, what it feels like, how it performs and if/how hard it’d be to get it to pass Bun’s test suite and be maintainable. I’d like to be able to co…

You can view it as an overreaction, but also as a sign that your work is significant. It impressed some, and scared others. In any case, you made something interesting.

You're replying to the original author of Bun. Given the usage of Bun, and the fact that his company (primarily him, actually) was recently acquired by Anthropic for what I'm guessing was a bajillion dollars, I think he probably already knows his work is significant and that he made something interesting.
Post reply on HN