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

Rust has been forked to the Crab Language

github.com

Post reply on HN
Print view View original

361–370 of 555 posts

Re: Rust has been forked to the Crab Language

#361

Post by smolder »

incrudible wrote: post #317
rowanG077 wrote: post #115

Honestly this bomb was waiting to burst for a long time now. Rust has aligned politically instead of just being a cool language. Bringing politics into something unrelated which brings people together is always a recipe for disaster.

But… the people who made it brought the politics. They own it. Rust is also not a cool language. You can not be cool and fuss about soundness and memory safety at the same time. It is mutually exclusive.

> You can not be cool and fuss about soundness and memory safety at the same time.

Well, that's just, like, your opinion, man.

Re: Rust has been forked to the Crab Language

#365

Post by unethical_ban »

Other than the title seeming to imply Crablang is now the canonical language, I see no problem with this as a casual observer.

They say they want to keep the fork in sync with "upstream", so they aren't trying to split the community away from Rustlang, but to have an alternative administrative structure.

Alright! That's always been a core feature of open source.

Re: Rust has been forked to the Crab Language

#366

Post by andsoitis »

nindalf wrote: post #192

This fork promises "All of the memory-safe features you love, now with 100% less bureaucracy!" Compelling, until you realise that all the commits are auto-merges of rust-lang/rust's main branch. Which means the same teams doing the same work, under a different name. Rust is experiencing growing pains because they're still figuring out a governance structure that works for everyone. They want to simultaneously keep th…

> they're still figuring out a governance structure that works for everyone

If they are indeed trying to figure out a structure that works for everyone, I’m afraid they’re pursuing a dead-end. One should be OK, in principle, to not aim for pleasing everyone.

Re: Rust has been forked to the Crab Language

#367

Post by Twirrim »

Dalewyn wrote: post #30
y7 wrote: post #6

The main website has an explanation for the reasons behind this: https://crablang.org/ More context: https://news.ycombinator.com/item?id=35583089

[flagged]

If it involves people, it will be political. There's absolutely zero way to avoid it short of it being a single-person project (and arguably even _that_ will be Political at the very least).

Re: Rust has been forked to the Crab Language

#368

Post by renewiltord »

I really like reading/writing Rust, but stay away from the community. Highest drama mainstream lang community ever but they've created a pretty good ecosystem.

Except for the actix fiasco, it's generally been quite chill as a user. You float above the twisting nether and grab what it throws out, which is pretty good.

Re: Rust has been forked to the Crab Language

#369

Post by nindalf »

starkparker wrote: post #358
nindalf wrote: post #192

This fork promises "All of the memory-safe features you love, now with 100% less bureaucracy!" Compelling, until you realise that all the commits are auto-merges of rust-lang/rust's main branch. Which means the same teams doing the same work, under a different name. Rust is experiencing growing pains because they're still figuring out a governance structure that works for everyone. They want to simultaneously keep th…

https://github.com/orgs/crablang/projects/4?pane=issue&itemI... > crab #51 > create experimental branch > opened last week > just need to create the experimental branch > it will start from the current state of our master branch, which is currently synced with upstream project but afterwards will not receive updates unless they can be incorporated without too many conflicts.

> This item hasn't been started

Open for a week. What's the matter, they're figuring out how to create a git branch? It's `git branch experimental && git push`, and running that would have been quicker than creating this ticket.

I wish everyone who read this thread yesterday could have also seen this - a shining example of the capabilities of the clout chasers involved in this project. They've delivered on their promise of "no bureaucracy" by avoiding software development altogether. Genius.

Post reply on HN