Earlier quoted context omitted.
There's plenty of precedent that states forks die, however to describe it as entirely futile is: A) Not exactly constructive. B) Possibly untrue. The move might indeed die, if the rust foundations leadership gets it's act together. Which is a strong push for them to sort things out rather than assuming everything will be fine with their current heavy handed and opaque approach. Failing this, we could be in a situatio…
In the examples you gave, either the original project shifted course significantly, or there are major technical disagreements. Here, pointless trademark drama is all there is, and the fork AFAICT replaced some strings and nothing else.
Rust has been forked to the Crab Language
51–60 of 555 posts
Re: Rust has been forked to the Crab Language
#52Re: Rust has been forked to the Crab Language
#53Now you can use Moral Rust for your hobby CLI projects and Fascist Rust at work.
Re: Rust has been forked to the Crab Language
#54Earlier quoted context omitted.
I share the spirit. OSS is all about forking. My company works with a very very niche TypeScript fork as well. Everyone should be free to work and contribute in the way he prefers for whatever reasons.
Forking a language that aims to be the long term stable systems language for a very large part of the IT landscape isn't a good thing.
Re: Rust has been forked to the Crab Language
#55The ultimate objective is to influence Rust stakeholders' decisions.
This is similar to a strike where ultimately your goal is not to destroy the company or to quit and leave, but to achieve better conditions. In both cases it sometimes works and sometimes not and in both cases, just because it might not work does not make it an immature move.
Re: Rust has been forked to the Crab Language
#56Interesting, how many negative comments this gets. People seem to love monoculture run by committees. This is exactly what OSS is all about. Take a code base and develop it into different directions. Both code and organization. And "natural selection" will have some forks die and others strife.
Re: Rust has been forked to the Crab Language
#57This happened a while ago and was related to the trademark/copyright issue. It’s an immature move and I can’t take this seriously. All this does is creating unnecessary drama surrounding the Rust foundation.
> All this does is creating unnecessary drama surrounding the Rust foundation. They are doing a fantastic job of creating drama all by themselves. I don't use Rust, but the constant childish bickering has turned me away from even caring to.
Re: Rust has been forked to the Crab Language
#58Earlier quoted context omitted.
This. Let a 1000 flowers bloom. There is an essay about it. To lazy to google it. Maybe some fellow has it bookmarked.
Let a thousand flowers bloom is a common misquotation of Chairman Mao Zedong's "Let a hundred flowers blossom". That slogan was used in the summer of 1957 when the Chinese intelligentsia were invited to criticise the political system then obtaining in Communist China. The full quotation, taken from a speech of Mao's in Peking in February 1957, is: "Letting a hundred flowers blossom and a hundred schools of thought co…
Re: Rust has been forked to the Crab Language
#59Forks of a large project seldom survive, they almost always die with no active development. This is a futile move.
Just look at LibreOffice. This is a fork of OpenOffice and OpenOffice is dead (at least to me)
https://blogs.apache.org/OOo/entry/announcing-apache-openoff...
Last commit made 3 days ago, actively maintained.
Re: Rust has been forked to the Crab Language
#60Interesting, how many negative comments this gets. People seem to love monoculture run by committees. This is exactly what OSS is all about. Take a code base and develop it into different directions. Both code and organization. And "natural selection" will have some forks die and others strife.