@aral Usually the meaning of "no politics" clause means "no off-topic politics", because it is usually: a waste of time; divisive; without beneficial effects on the real-world.
You cannot solve all the problems of the world in a project. So you had to decide what are on-topic business politic decisions that are worth to discuss and share, and what it is outside of project scope.
@hayley we can annoy you better... I'm suggesting to the blamer (in a private message, of course) a rant about Lisp (SBCL) GC!
@jesus
Common Lisp is very performant and for large code bases it is probably faster than many C++ projects, because you can customize a lot of things about the memory layout of objects.
CLOS with MOP is very efficient (the OOP part of Common Lisp), and Common Lisp macro can give you all the benefits of C++ STL, and probably more.
@jesus It is only the first impression. I thought the same. Now, it is one of my preferred syntax.
But we are offended because you missed to offend explicitly also Common Lisp in the list! We prefer to be offended than being ignored! 🙂
@ramin_hal9001@emacs.ch
So it must be read as:
"Note that the `anon` (Linux) user is able to become `root` (Linux user) without password by default, as a development convenience.
To prevent this, remove `anon` (Linux user) from the `wheel` (Linux) group and they (who!? ah the real-life users logged as the `anon` Linux user) will no longer be able to run `/bin/su`."
I'm not convinced. It is against Occam's Razor. It is simpler to read as "... and it (the `anon` Linux user) will no longer be able to run `/bin/su`".
But it is not really important. Only for sake of discussion.
@louis@emacs.ch
@ramin_hal9001@emacs.ch thanks for the polite answer!
Regarding the grammar, that obviously is not the main point of the discussion, I disagree.
If you are correct, it should be something like
"Note that the `anon` users are able to become `root` without password by default, as a development convenience.
To prevent this, remove `anon` users from the `wheel group and they will no longer be able to run `/bin/su".
But from a technical point of view `anon` is a user in Linux, not a group of objects. So probably I would use "it", instead of "he/they", because it can be seen as a "role", and not as a person:
"To prevent this, remove `anon` user from the `wheel group` and it will no longer be able to run `/bin/su`.
@louis@emacs.ch
@ramin_hal9001@emacs.ch I'm curios.
Our language is imperfect. You can change/improve it, but it requires time. During the transition, it is also a matter of personal style.
Accusing someone to be "probably" racist, only because he does not agree with some new form of written style, is rather extreme. I'm scared more from you than Andreas Kling, because you are giving me vibes of the "Reign of Terror" during the French Revolution.
This is one of the refused pull-requests https://github.com/SerenityOS/serenity/pull/6814/files
The "they" makes the sentence more ambiguous because without technical knowledge it can be interpreted as "the `wheel` group will no longer be able to run `/bin/su`.
So using "they" everywhere is not always a good solution, and after you accept one modification, you had to change documentation in all places, if you want to be coherent. So, it is not a single fix, but a "political decision".
Changing the language is a political action, but also refusing to adopt the new style is a political decision. But, it is more normal sticking to actual conventions, than adopting new ones. The usual solution is creating a new fashion, and waiting that the people following old fashions will naturally change or die. But not "killing" them!
You can fork the project, and use your conventions in your new community, but accusing the other to be a "racist" and to not deserve money for a project he created, only because he sticks to old and usual conventions, is too much extreme.
@louis@emacs.ch
It is a shame that in 2024, 35 years after Richard Stallman created the GPL, there is no EU or USA or international treaties taking in account copyleft licenses rights.
If a company A violates the GPL license, using the source code of a product P in a closed source product, then only the original authors of the product P can sue the company A, and only for the parts for which they own the copyrights.
Users of P and normal citizens cannot sue A. They have no "rights" to defend.
@unknow tutto vero, ma è anche vero che all'epoca Berlusconi dipingeva il PD come un partito nostalgico delle idee comuniste della Russia di Stalin, quando i problemi di nostalgia malriposta si è scoperto averceli invece la base giovanile della destra.
Inoltre FdI ha sempre negato di avere questi problemi, mentre ora si può affermare che l'acqua bolle a 100 gradi e alcuni giovani attivisti di FdI ci vorrebbero far bollire gli ebrei.
@hayley It was clear at first look, only observing the formatting, that this is a FEDIVERSE POST full of deep CONTENT! 😃
@hayley usually you answer in this way for saving time and energy, filtering out cranks people, i.e. not-expert people committing common naive errors. But as any heuristic, it is not infallible and you can filter out valid criticism. It is a trade-off.
As you said, the real answer should be in showing the faults in the opposite assertions. Otherwise, it is not science but cargo-cult.
@freemo I'm happy you found the AI expert, and you are testing this new AI bot speaking about ultraditionalist-catholic-trans. 😃
@ovid only an ignorant and clueless person may consider important the capitalization of Lip/LISP/lisp name! All the world knows that Lisp syntax is case-insensitive! 🙂
@sj_zero true and interesting. But the real problem is that nowdays "uncontrolled" capitalism is causing too much problems, because we entered in a mass-extinction era, so we will loose all the benefit gained in the past.
So the assertions "Capitalism is the cause of all the world's problems" is not 100% correct, but it is more true than false.
We need to reform/improve capitalism and/or democracy rules.
@civodul
an evergreen book is https://en.wikipedia.org/wiki/Getting_Things_Done
In the "perspective" section, the author suggests to reflect weekly about the mid-term, and long-term objectives, and in case change something.
@nando
I'm trying to switch from NixOS to GuixSD, mainly because in case of problems I prefer to debug Guile code, than Nix code. There are more tools for Guile than Nix, and it is more elegant.
Guix community has less package, and it is focused more on perfect bootstrapping. So, up to date, for example, it cannot support directly Java Gradle based projects. There are also problems with nodejs packages. Nix instead has no problems in taking shortcuts, and it has an impressive number of packages.
If something works in Guix, usually it works very well. In some cases, also better than Nix. I like it a lot.
@schmittlauch
if you are physically harmful to other persons, you cannot stay in the same event with them, and there can be also police investigations. So, usually people with accusations are banned from the event, waiting for the trial or quick double-check from the organizers.
There can be also false allegations, and the sad part, it is that often there are no consequences for the false accusers. But this is another story...
But if you are a serial-killer, sending pull-requests from your prison, using a nick-name, then these PR should be reviewed only according the technical details.
If you buy a car, and you are polite, they do not check how you earned the money. In a software project, the currency (i.e. substance) is the code, and the form is how you interact in the community. All other aspects are hard to enforce, and there can be dangerous side-effects.
good points.
A rule must be clear, otherwise its application can be abused and it becomes a dangerous rule.
Moreover, you can ban in an effective way "sexism", "racism" and "fascism" from a community, specifying that these type of messages are not allowed in the communication channels. They are simply off-topic respect software development.
But it is dangerous if you declare to ban "sexist", "racist" and "fascist" people, because: there can be a "fascist" who is a good contributor and he is not violating the CoC during his interactions in the project; corrupt people can ban someone they don't like, only accusing him to be a "fascist".
French revolution had good ideals, but it created also "The Reign of Terror".
@screwtape
I skimmed your links. To be fair, it seems one of the many/few academic projects, about AI and collaborating agents, and so on.
They are hard to evaluate, because many of them sound logical and well designed, but IMHO only usage in real-world scenario can tell the truth about their effectiveness. For example, there are many types of logical theories that can be used.
I'm usually interested to these topics. I have also some project to finish, on these topics. Maybe some day...
I'm a software developer. I live in Italy.