401–410 of 555 posts
Earlier quoted context omitted.
Human rights are not political unless you're trying to reduce them. Mozilla justifiably did not want to work with someone who opposes certain human rights (including those of other employees), and that shouldn't be controversial or political.
What do human rights have to do with any of this? Isn't this about trademarks?
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…
Earlier quoted context omitted.
Human rights are not political unless you're trying to reduce them. Mozilla justifiably did not want to work with someone who opposes certain human rights (including those of other employees), and that shouldn't be controversial or political.
What do human rights have to do with any of this? Isn't this about trademarks?
Earlier quoted context omitted.
libav was the hostile fork, not FFmpeg. Someone removed write permissions from key contributors (or contributor. I forget) and just about everyone sided with those contributors, thus the instigators were forced to rename their project. The development effort stayed on FFmpeg, even as the libav people tried porting back the changes. Eventually libav passed into irrelevance as it failed to acquire mindshare and distrib…
It's been a while since I read the story but I believe it did prompt some changes in ffmpeg management, that's why I was saying it was a hostile fork success story.
It's a whitelabel copy based on policy disagreements, not unlike the "Iceweasel" (now Debian Firefox-ESR)[0] fork of Firefox. Just dawned on me after I wrote the first sentence that both actions targeted Mozilla offspring. [0] https://wiki.parabola.nu/IceWeasel_History
Earlier quoted context omitted.
> Sure, Crab will almost certainly not replace Rust, but that is not the goal. I see it as: there's a finite amount of people who choose to dedicate their unpaid free time contributing to making Rust better (working on fixing bugs, new features, etc.) This seems like fragmentation which basically will slow down progress. Now, obviously the people who choose to dedicate their free time to open source software are enti…
Not to downplay any of your points, but as a counterpoint, I'm not sure this was true for Vim/Neovim. Perhaps I'm only looking at short-term gains though and not long-term fragmentation
Earlier quoted context omitted.
As a direct result of Stallman's uncompromising disinterest in what values people in the broader world actually wanted to engage with -- instead attempting to dictate his own moral views as a petty tyrant -- GNU _as a project_ hasn't been relevant to computing for decades. When was the last time you booted up the Hurd kernel? I would be surprised if more than 10% of HN readers even know what that is. (Stallman actual…
GNU wants to recreate a 1988 Unix. That's not necessarily a bad thing – I'm an old Unix beardy type myself as well – but it's not really how you stay at the forefront of computing, yeah. Also didn't help Stallman alienated the GNOME and GTK people so they're not longer GNU projects (and they were independent for a long time before that anyway). There are still some important GNU projects though, GCC, GNU libc, and Gr…
Except he's pissed off most of those people too.
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…
Interesting, 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.