4 ms·
RMS is micromanaging Emacs in a user-hostile and developer-hostile way. RYF is a disaster that accomplishes nothing. FSF/GNU has a habit of forking or rewriting
by wmf 4y ago
RMS is micromanaging Emacs in a user-hostile and developer-hostile way. RYF is a disaster that accomplishes nothing. FSF/GNU has a habit of forking or rewriting existing free software to make it "more free" but delivering no actual benefits to users, like gNewSense, Libreboot, Guix, and GnuTLS.
- 2muchcoffeeman 4y agoThen fork it and run it in the way you see fit.
- Dylan16807 4y agoThe existing software is already that fork, isn't it? Even ignoring the other reasons that lazy counter is bad to throw out.
- skissane 4y agoXEmacs was a fork of GNU Emacs, driven by technical and philosophical disagreements with RMS. For a while it was rather popular, but then it died. Its failure is a counterargument to these complaints about RMS' management style–if his decisions are really as bad as some people say, why didn't the fork succeed? And why won't any of the complainers start up a new fork themselves, or revive the moribund XEmacs fork? You might be thinking of GCC – the current GCC is descended from a fork of GCC (EGCS). RMS agreed to let the forkers take over the official project. GNU Emacs itself is a fork of Gosling Emacs. The original Emacs was written in TECO, a rather horrendous language. Soon, people started writing Emacs clones in Lisp – Multics Emacs, and some of the Lisp Machine editors. James Gosling wrote the first Emacs for Unix platforms; for an extension language, he invented "Mocklisp", which resembled Lisp on the surface, but lacked its power and generality. GNU Emacs started out as a fork of Gosling Emacs, adding a real Lisp instead of Mocklisp. Gosling made his Emacs freely available under an unclear license, and then sold it to a commercial firm and declared its original free distribution rescinded. To get away from that legal problem, RMS rewrote all the remaining Gosling Emacs code.
- pjmlp 4y agoSome of us found in XEmacs the escape route in the lack of IDEs on the UNIX world. XEmacs failed, because eventually IDEs became a thing on UNIX platforms and that is where we went, to the toolset we were missing, not Emacs.
- wmf 4y agoThat's already done. For example, Ubuntu has probably brought more people to free software than Debian. The argument I and other people are making is that the FSF's goals are being achieved but not by the FSF.
- 2muchcoffeeman 4y agoSorry. I didn't read your comment as a criticism of the FSF because they don't live up to their ideals. And you didn't initially provide an organisation that did it better. That's fair enough.
- bruce511 4y agoTrue. Open source software is waaay bigger than Free software. And free software delivered by the FSF is a drop in the bucket of all software-available-in-source-code-format. This is not a bad thing, nor a reflection that the FSF is doing it wrong. Indeed it is a sign they are doing it right. Ultimately all open software exists _because_ of the FSF. They set the marker in the ground, they set the standard the rest if us don't quite live up to. Their role is not to produce all the code, their role is to explain the freedoms well enough so that enough other people believe in some, or all, of those freedoms. The two main threads of the article are hardware, and emacs. Depending on how far down the stack you want to go (open microcode in your CPU?) it's generally possible to get hardware open enough for you to do anything you like. Not all hardware is open, sure, but there are enough choices. Yes there are still closed drivers (ironic given what kicked RMS off in the first place) but careful choices play a role here. That said, keeping an eye in the hardware, and keeping open hardware in our minds, is an excellent reason for the FSF to exist. Their job is not to win the war, its to make us care about the war at all. We will win it, if we care about it. Emacs is a very specific example of a program run by a person who has beliefs. He builds that program to conform to those beliefs, not the beliefs of his user base. In this case he's the printer maker not wanting his printer to work on the new hardware. His goal is not to make "the world's best editor" - his goal us to "make the world's best editor that promotes free software ideals." Ironically, if you don't like that, you can take his work and built on it however _you_ like. He not only represents the original problem, he presents the ongoing solution. The Freedoms are explicit. They don't give the user rights over the developer. They give the user rights to add their own work to the equation. Emphasis on work. The FSF is not fighting the wrong war. They are not fighting at all. They are setting a marker in the ground saying "this is what could be." Our job is to notice, and care.
- deleted 4y ago[deleted]
- creatonez 4y agoGNU Guix is way different from upstream (but that's about it, in terms of GNU forks that actually offer value)
- 3836293648 4y agoUpstream in this case is NixOS, even if very little actual code ended up being used (basically just the builder/evaluator daemon)
- llanowarelves 4y agoI sympathize with your overall cautionary sentiment but have to push back on it as it pertains to Guix not adding value. I chose to use Guix SD because I like that the config is in a real (more general purpose) language, which I then proceeded to learn. From what I understand (someone that knows Nix can chime in) the Guix CLI is also more parsimonious than the Nix CLI, and not multiple differently named tools. I like the simpler interface this provides. It is however a bummer that there's no socially-approved way to share packages of non-free software on the official channels (what are the unofficial channels I should know about? Just have been searching Github to find).
- forgotpwd16 4y ago>not multiple differently named tools. I like the simpler interface this provides They've been working towards this with the (introduced[0] in v2 few years ago) experimental `nix` command that combines the various `nix-*` commands. [0]: https://nixos.org/manual/nix/stable/release-notes/rl-2.0.html#:~:text=new%20command%20named%20nix https://nixos.org/manual/nix/stable/release-notes/rl-2.0.htm...
- grumbel 4y agoNixOS has had the new `nix` command for a long while, this bundles up all the functionality under one command just like `apt` or `guix`. It's still marked as experimental and has to be enabled manually, but once done you'll never have to touch any of the old commands ever again. The only problem left is that a lot of the documentation still refers to the old commands. > It is however a bummer that there's no socially-approved way to share packages of non-free software on the official channels There is https://gitlab.com/nonguix/nonguix https://gitlab.com/nonguix/nonguix That's one thing I prefer about NixOS, with Nix Flakes you can just turn any old Git repository into a package. No need to be part of any channels or need for the user to setup anything, you can just build and install straight from the upstream source with a single command line if they provide a `flake.nix` file. This automatically resolves a lot of pointless drama about what should or shouldn't be part of the distribution and makes it trivial to distribute patches and workarounds.
- 4y ago
- rekado 4y agoI suggest you update your mental model of what Guix is. If you only see it as a rewrite of Nix you're missing out. I agree that the knee-jerk reaction of many FSF or GNU-adjacent developers to start a "filter" project that takes upstream and removes parts of it is regrettable.
- singpolyma3 4y agoThe trouble with RYF I think is timing. If it came at a time when the movement was strong and had a large mindshare, then getting certified would get you a market and might be attractive to some vendors. As it is, the RYF market is so small that no vendor is incentivezed by it unless they are part of the movement already themselves.
- naasking 4y ago> FSF/GNU has a habit of forking or rewriting existing free software to make it "more free" but delivering no actual benefits to users "More freedom" is a benefit. You're free to judge whether it's a benefit specifically to you, but you can't judge that for others.