Live data from Hacker News

Rust has been forked to the Crab Language

github.com

251–260 of 555 posts

Re: Rust has been forked to the Crab Language

#251

Earlier quoted context omitted.

So it didn't survive then. Isn't that the whole point of what I said: > Forks of a large project seldom survive.

But it did survive. I can't view rejoining the forked from repository as dying.

Who is still using the io.js fork? Nobody?

That is my point.

Re: Rust has been forked to the Crab Language

#253

Forks of a large project seldom survive, they almost always die with no active development. This is a futile move.

It worked for io.js when they split off from node.js. When io.js was re-merged in with node, the project was all the better for it. They ultimately improved Node's release schedule and cadence, governance, etc.

An issue with this analogy is that io.js addressed major problems that the community was aligned with. That isn't the case with this repo, which is just a replacement of the word 'rust' with 'crab'.

Re: Rust has been forked to the Crab Language

#254
post #73

Earlier quoted context omitted.

You are implying that the only measure of success for a fork is for it to exist indefinitely. If the goal of io.js was to improve Node's governance model, which appears to be the case, then I would consider it a success.

> Forks of a large project seldom survive. The fork died. that is the point. goal or no goal.

ok but that's a terrible point

Re: Rust has been forked to the Crab Language

#255

Earlier quoted context omitted.

Precisely. The naivety on display here about the realities of long term software development is absolutely astounding, especially for a project with such lofty goals. Keep your dirty laundry out of the public eye if you really care about Rust.

I agree with you on the “realities of long term software development”. But I think I believe there is a fundamental difference between the standard realities on a successful enterprise project and the language itself . That is, the latter needs to balance the needs of a much, much wider array of customers (all rust compiler users) versus the former with a more specific target user base. This introduces different requ…

If you can't resolve that conflict of interest then you have absolutely no business being near the seats of power for a project such as Rust. Rust needs to be perceived as a safe bet, not as the next Ruby, if it is to achieve the goals that have been put forward by those that advocated for the language's adoption.

Re: Rust has been forked to the Crab Language

#257
This will go nowhere. That's sure.

It has exactly zero technical advantages over the original. It has not even the plan to add any improvements over the original… The plan is just to merge upstream.

It has no funding. (And a project of this sized needs a lot of funding, just to get the day to day maintenance going.)

This whole thing is completely pointless. I'm wondering why it gets so much attention.

Re: Rust has been forked to the Crab Language

#258
post #35

For anyone critizing this: From the trademark bullshit to the conference drama, it's clear at this point that someone with influence in the Rust foundation is behaving like an asshole and damaging the project. That can happen in open source, see Stallman and others. It's also clear that others at the Rust foundation tolerate this behavior, downplay it, don't understand the impact, don't want to go against a "respecte…

Okay this is fine but will they have the commercial backing that Rust has from the likes of Microsoft and Mozilla and others? Are the languages different? Is the fork just to fix the management or will the languages diverge/have they already?

Re: Rust has been forked to the Crab Language

#259
post #35

For anyone critizing this: From the trademark bullshit to the conference drama, it's clear at this point that someone with influence in the Rust foundation is behaving like an asshole and damaging the project. That can happen in open source, see Stallman and others. It's also clear that others at the Rust foundation tolerate this behavior, downplay it, don't understand the impact, don't want to go against a "respecte…

ffmpeg vs libav is one case where I think the hostile fork ended up working well.
Post reply on HN