One software freedom that Stallman does not mention is the freedom *not* to use the program because you dislike or don't want it for some reason

Free software tends to be flexible, have clear boundaries, split responsibilities, and replaceable components, thanks in part to openly defined protocols and formats

Proprietary software tends to want to lock you in into their freaking ecosystem, and even if they adopt an open standard, it's a part of an E-E-E strategy

@bugaevc Of course Stallman doesn't mention this one, GNU is basically doing vendor lock-in with their numerous poorly-documented extensions.
Also he doesn't seems to like LLVM/Clang because it allows to use some basically reversed GNU extensions outside of GCC.

@lanodan which undocumented extensions are you talking about? Sure, the Hurd, GNU libc, GCC, etc. all extend classical Unix/C in interesting ways, and the documentation is not always perfect; but that's just from a lack of manpower, not an act of intentionally locking people in. In fact most GNU software is written in a way that *doesn't* require other GNU system components or extensions, making it very portable. This is the opposite of lock-in.

(1/2)

@lanodan he's made it very clear why he opposes clang/LLVM, and it's not on a technical basis:

"The existence of LLVM is a terrible setback for our community precisely because it is not copylefted and can be used as the basis for nonfree compilers -- so that all contribution to LLVM directly helps proprietary software as much as it helps us."

gcc.gnu.org/ml/gcc/2014-01/msg

(2/2)

@bugaevc
GNU: Oh no LLVM is not restrictive enough on it's license!
Also, GNU: uses a license so restrictive on GCC it's unusable in a BSD base system.

Also not on a desktop right now so can't give many links but GCC has all theses extensions on C: https://gcc.gnu.org/onlinedocs/gcc-9.2.0/gcc/C-Extensions.html
And none of the ones I looked into where documented enough to allow a reimplementation in another compiler.

@lanodan clearly, you're in a "permissive is better than copyleft" camp. That's alright, but other people have different opinions on this (namely, on what's better in the long run); that's not the reason to hate GNU or think they're hypocritical.

(1/3)

Follow

@lanodan I think copyleft is better, and (most of) my software is under GPL. That doesn't mean I call out everybody who chooses a permissive license for their projects, but I may chose not to use their software if there's a copyleft-licensed alternative that I find better (or not much worse).

(2/3)

@lanodan This quote from Linus Torvalds sums it up:

"Nobody has the right to whine about another persons choice of license. You have a choice: use it or don't. Complaining about the license to the author isn't part of it."

All those GNU C extensions seem pretty well documented to me. Not that I'm developing a C compiler...

(3/3)

@bugaevc In my experience, the C language and good documentation is not something that comes well in the same sentence. Probably because I've seen so many scientific articles in the past years that claimed to have finally understood (through very heavy mathematical models) what the C standard meant by a particular word… and then to add that well-known compilers have different interpretations of this 😕 This is not directly related to these extensions, of course, but the C language itself is pretty ill-defined per se, which doesn't help extensions.

@bugaevc @lanodan hi I have developed a C compiler and those GCC extensions are the underspecified bane of my existence

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!