once. But he passionately denies there were any hookers involved.
@sun @newt @kirby People also really like to assume that he’s like super autistic virgin loner or and someshit.
But that’s not true at all. He’s got a regular private life with family and friends, but he just keeps those things private and away from the internet.
And the fact that little is publicly known about his private life is unfortunately what makes people fill in the blanks with that terrible bullshit I think.
complete nonchalance and lack of boundaries. Seems consistent with his email style.
@sun @kirby @SuperDicq @newt miguel de icaza worked for ms until 2022
@bonifartius @sun @kirby @newt Oh right it’s that Miguel de Icaza. I knew I recognized the name from somewhere.
Whatever he says he is definitely not someone who is to be trusted.
@bonifartius @sun @kirby @newt I know Miguel is “the founder” of a bunch of notable free software projects.
But I also don’t have very high opinion of the “founder” type people who only are here to “found” projects and then immediately leave to go “found” something and instead of actually sticking with the thing and growing it to fulfillment.
@newt @sun @kirby @bonifartius I mean I get it though. Yes he made sure it was completed to version 1.0 which can count as “fulfillment”, but it is very different from people like Stallman who dedicate their entire life to the movement instead of just a few years and then move on to something else.
has done other than writing emails, giving speeches, and maintaining Emacs. He certainly hasn't succeeded in giving birth to any kind of GNU OS or a free (as in speech) computer of any kind.
@newt
Hella charisma for someone that looks the poster child of a Reddit mod.
@newt @bonifartius @kirby @sun Just because Stallman is no longer a programmer doesn’t mean he has abandoned it. He is still Chief GNUisance the leader of the GNU Project.
Abandoning it like Miguel would mean he now would go around suggesting people should use MSVC instead.
@newt @sun @kirby @bonifartius People switched to LLVM because they are proprietary software lackeys that don’t want to abide by copyleft and give other people the same freedom they have.
was very vocal against splitting GCC into separate backend and frontend parts and stabilising the IR. This alone had done massive damage to Linux development tooling for years. We could have had working autocomplete, error highlighting, and other cool things in the early 2000s. Instead, we had to wait for clangd for another 15 years.@newt @sun @kirby @bonifartius Yes, some implementations of LLVM is free. Using a free version of LLVM is not a sin, but a penance.
@SuperDicq @newt @sun @kirby @bonifartius
give other people the same freedom they have.
GNU isn't about freedom, it's about forcing restrictions on everybody else.
through his influence has held open source (or free, or whatever you want to call it) software back and caused a lot of irreparable damage. This is really why I despise his character, not because he screwed some hookers or said nasty things to people.
@phnt @newt @sun @kirby @bonifartius Telling others to pass on the same freedoms that they have is not a restriction, silly.
@phnt @kirby @SuperDicq @sun @newt is someone going around with a gun, forcing people to use gpl licensed software?
@SuperDicq @newt @sun @kirby @bonifartius s/telling/forcing
Read the license, it is not a choice.
@phnt @newt @sun @kirby @bonifartius You shouldn’t be allowed to take other people’s freedom away. For reasons things like murder are illegal.
@SuperDicq @newt @sun @kirby @bonifartius Correct, I should have freedom to use your software however I want and do whatever I want with it. But GPL is not compatible with that, owner of the copyright is a dictator that forces restrictions on how the software is used, modified and distributed.
@phnt @newt @sun @kirby @bonifartius Copyleft is not a restriction, it is freedom preservation.
If you were already doing the right in the first place (making free software), the GPL doesn’t do anything.
@SuperDicq @bonifartius @kirby @newt @sun Let's take your thinking exactly as you say. License everything under OpenWatcom/Sybase. If you are writing free software already, you intend to share it with the public right? Isn't that what everybody should be doing, sharing their code?
@phnt @newt @sun @kirby @bonifartius Why should taking other people’s freedom away be allowed?
@phnt @bonifartius @kirby @newt @sun No, of course not, the Sybase Open Watcom Public License is a nonfree license. It has actual restrictions unlike the GPLv3 where it for example requires you make all your changes public.
@SuperDicq @newt @sun @kirby @bonifartius So when a license has stronger freedom preservation and protection, it's suddenly no free. Alright.
@phnt @newt @sun @kirby @bonifartius Requirimng people to publish their private modifications has nothing to do with freedom preservation.
@newt @phnt @sun @kirby @bonifartius In my country any form of murder is illegal, and I consider countries that have a legalized forms of murder, such as the death penalty, to be very uncivilized.
@SuperDicq @newt @sun @kirby @bonifartius Yes it does. I can modify GPL code however I want, but as long as I keep it internal, I don't have to share it with anyone. There are companies I know that have private kernel patches that will never be shared upstream and they are internal. Perfectly legitimate thing to do according to GPL. How is that freedom respecting and inline with the GPL spirit. It's simple, it isn't.
@phnt @newt @sun @kirby @bonifartius It is completely freedom respecting to keep private changes to yourself. You have a right to privacy. You are not denying anyone freedom by keeping private things private.
@SuperDicq @newt @sun @kirby @bonifartius So it is freedom respecting to keep private changes to yourself, but it is not freedom respecting to keep changes for your products you sell to yourself. Whose freedom are you breaking then?
@phnt @newt @sun @kirby @bonifartius If you are are selling software and you are not willing to give them the source code, you are denying your users the freedom to modify it.
@SuperDicq @newt @sun @kirby @bonifartius And you are not denying your users the freedom to modify it, when you are using a private change that makes you higher profits that isn't the product you are selling itself? The product only benefits from those changes and aren't in the product itself. Aren't you denying the freedom to modify and include that change to everyone upstream?
@phnt @newt @sun @kirby @bonifartius I don’t even understand what you’re trying to say here.
On private code you are not denying your users anything because there are no users except yourself.
@SuperDicq @newt @sun @kirby @bonifartius I've described the typical SaaS scenario. Kernel has a private change that does not need to be public, but the product, a webapp, uses that change for higher profits, in other words, you still selling a product, you've just hidden the private change one layer down. Effectively doing the exact thing that GPL enthusiasts laugh at BSD/MIT for enabling.
@phnt @newt @sun @kirby @bonifartius SaaSS is indeed proprietary. To solve this issue that’s what we have AGPLv3 license for.
@SuperDicq @newt @sun @kirby @bonifartius Even the AGPL does not solve that. The webapp can be free software under AGPL using a feature nobody else has access to. And licensing the kernel under AGPL would be a licensing disaster.
@phnt @newt @sun @kirby @bonifartius That’s true the AGPLv3 only guarantees freedom for the software the user directly interacts with and not the other software on the system, such as the kernel.
And yes, it is true that the GPL license family doesn’t solve all freedom issues, but it is a good attempt to do so, much better than permissive licenses.
@SuperDicq @bonifartius @kirby @newt @sun The only way to solve the issue is to use Sybase or abolish copyright and make exfiltrating private source code legal.
Or how will you make the kernel comply with the requirement to give you a pointer to it's source. Reserve a port that when you hit with Telnet, prints you the links for every public device running Linux on the planet?
@phnt @bonifartius @kirby @newt @sun No, Sybase is a deeply flawed license philosophically. It doesn’t solve software freedom issues.
If I interact with your webapp I don’t need the source code of the kernel that you use. I am not directly interacting with your kernel. That is acceptable.
@SuperDicq @newt @sun @kirby @bonifartius Depends on the interpretation. You are interacting with a public machine running a kernel hypothetically licensed under AGPL. You are not only interacting with a web app, but also with the server running that web app with TCP/IP.
@SuperDicq @bonifartius @kirby @newt @sun Of course kernel unter Sybase also solves this, because you have to publish the changes no matter what.
@phnt @newt @sun @kirby @bonifartius What is the issue here? If I want to run a local copy of the webapp, I can still do that without your custom kernel.
@SuperDicq @newt @sun @kirby @bonifartius The webapp doesn't have to run without a modified kernel. Or any dependency it needs for that matter. Even a modified PHP would fly if PHP was GPL licensed.
@phnt @newt @sun @kirby @bonifartius If your AGPL licensed program has proprietary dependencies, it is not free software.
@SuperDicq @newt @sun @kirby @bonifartius Doesn't have to be proprietary. If you wanna be really evil, it can be a GPL interpreter with a custom private encryption scheme that decrypts the AGPLed webapp on the fly. Effectively exactly what is Denuvo and VMProtect, but with a GPL dependency whose source does not have to be published and a AGPL webapp.
@SuperDicq @bonifartius @kirby @newt @sun You can release the encrypted/obfuscated source code under AGPL and users are left in the dark.
@phnt @bonifartius @kirby @newt @sun If you’re releasing the source code in obfuscated or encrypted form only you’re not abiding by the AGPL correctly.
@SuperDicq @newt @sun @kirby @bonifartius I think you could get away with it rather easily. The AGPL is mostly just GPL with a network clause that basically says, if it is available over the network, you have to make the source public. GPL does not talk about obfuscated or encrypted source code, it only talks about source code and binary form. And obfuscated code that demangles on the fly isn't a binary form.
At worst, the license does not apply and you don't have to release it if you own the copyright for everything.
@phnt @newt @sun @kirby @bonifartius
GPL does not talk about obfuscated or encrypted source code, it only talks about source code and binary form.
No, you are mistaken. It talks about “Corresponding Source” which is defined as the “the preferred form of the work for making modifications to it”.
An obfuscated or encrypted source code is obviously not “the preferred form”. No court is going is going to agree with is.
@SuperDicq @newt @sun @kirby @bonifartius Still, point still stands. You have to either abolish copyright or use Sybase unless you accept being cucked by an already abused loophole that effectively nullifies what the GPL stands for and turns it into a BSD license. Unless you sell a product directly with the change or it's in a user facing public webapp.
@phnt @newt @sun @kirby @bonifartius
Debunk the point
Point still stands
That’s not how a discussion works bruh
@SuperDicq @newt @sun @kirby @bonifartius Nope, I'm taking about my previous point before you sidetracked the thread into a tangent why AGPL fixes this (it still doesn't, you just can't fully DRM the source).
@SuperDicq @bonifartius @kirby @newt @sun Also the web app can still depend on a private change to a GPL dependency. AGPL allows GPL dependencies and thus allows this unintended behavior.
@phnt @bonifartius @kirby @newt @sun Like I said before if it has nonfree depedencies that makes the software nonfree, despite it having a AGPLv3 license.
@SuperDicq @newt @sun @kirby @bonifartius GPL is a free license. It just allows you to do this loophole.
@newt @phnt @sun @kirby @bonifartius Usually these cases are settled outside of court for way less money because the license is solid and the parties often do not want to go to court over it.
@newt @kirby @SuperDicq @bonifartius @sun remember that the fsf had to be essentially dragged into the neo4j case after it threatened the legitimacy of the GPL. They didn't really want to get involved until then.
@newt @SuperDicq @bonifartius @kirby @sun Last time the GPL had actual teeth was with NeXt and the objc gcc frontend. Nothing major since then.
@newt @phnt @sun @kirby @bonifartius The Linux Foundation doesn’t care about enforcing the GPL. It’s a really bad foundation.
@SuperDicq @newt @sun @kirby @bonifartius It doesn't care about Linux either.
🌿
🌿
@mangeurdenuage @kirby @SuperDicq @bonifartius @sun @newt
which is what the GPL does
It does not. GPL in every way is freedom restricting compared to any other free license except Sybase. The whole point of it is to restrict what you are allowed to do with the code and when you have to distribute it. There's nothing "freedom" about that. 0BSD is much freedom respecting, it says you can do anything with it except that there's no warranty. That's a true freedom respecting license. The freedom to use, modify and distribute software however you like.
You can also blame my stance exactly on opinions of people like you. I didn't use to have these opinions until I read posts like these every other day.
🌿
🌿
last I checked, he did it entirely for the love of the game.
🌿
is a sign of mental distress. No corporate slander required tho.
@mangeurdenuage @kirby @SuperDicq @bonifartius @sun @newt
We already know where the permissive proprietary path leads us,
Yes, I know where the path leads. To less broken GNU software, because they finally will have competition. So far the less GNU on my systems, the less broken they are. Mysterious, I know.
@newt @kirby @SuperDicq @bonifartius @mangeurdenuage @sun
last I checked, he did it entirely for the love of the game.
He still does. Just not as frequently. The next time you seem some nonsensical software related drama on here, check his blog. The likelihood it came from there is rather high.
🌿
@mangeurdenuage @kirby @SuperDicq @bonifartius @sun @newt
Lol. Competition between black boxes, what a silly concept, as if the 70s/80s didn't experience that already. Be ready to pay for each individual compiler option fuck boy
You have no idea how bad GCC would be today if llvm and clang didn't exist.
🌿
@mangeurdenuage @SuperDicq @bonifartius @kirby @newt @sun Also for extra fun, look who maintains most of your GNU projects. It's IBM via Red Hat as a proxy.
@phnt @kirby @SuperDicq @bonifartius @mangeurdenuage @sun GCC is still bad tho. It's one of the few compilers where you need a completely separate build for cross-compiling. If you wanna build a golang program for another architecture, you can just run GOARCH=arm GOOS=linux go build. Similarly, with clang: clang --target=aarch64-pc-linux. Meanwhile, GCC can't do this.
Basically, the main reason why people avoid cross-compiling and instead run native builds either on hardware or in VMs is because GNU tooling horribly sucks.
was
@newt @mangeurdenuage @phnt @kirby @bonifartius @sun This “failure of a leader” achieved a thousand times more than you ever will.
🌿
clearly stated they were presented as consenting and adult.
comments on sexual relations with minors and age of consent? Because I tried to avoid this subject here. The aforementioned Drew Devault made a nice list of them with references, by the way.
@newt @mangeurdenuage @phnt @kirby @bonifartius @sun Drew Devault has said worse things than Richard Stallman.
@newt @mangeurdenuage @phnt @kirby @bonifartius @sun And Stallman has apologized for his statements and retracted them, Devault pretends it never happened and tries to hide it.
🌿
was a bad leader for a software foundation and a bad maintainer for GNU projects. My arguments are listed above. Whatever he thinks about the age of consent and sexual relations is irrelevant here. I've no idea why @mangeurdenuage decided to pull this here.
🌿
🌿
@newt @kirby @SuperDicq @bonifartius @mangeurdenuage @sun Which is quite ironic when GNU/Autohell isn't that bad at setting up cross-compiling. If you already have the toolchain that is.
Another thing that GCC sucks at real bad along with GNU/Autohell is setting up static builds. I love passing --disable-shared/--enable-static and still have a binary that dynamically links to the libc. Completely disregarded the assignment and glibc not being statically linkable is not an excuse for this behavior.
level paranoid, I'd claim that Autohell was an intentional sabotage against open source ecosystems.