Shamar @Shamar@qoto.org

... good enough except for the #SelfDriving part in #selfdrivingcars ...

@eldaking
QT: https://mastodon.social/@eldaking/103561844836336624

@freemo ops... sorry

... good enough except for the #SelfDriving part in #selfdrivingcars ...
QT: https://mastodon.social/@eldaking/103561844836336624

“There is no such thing as a neutral tech platform”

https://www.nature.com/articles/d41586-020-00160-y

@jasper

And... I guess that calling me "retarded" is perfectly compliant with your #CoC! 🤣
(like if it was an insult, also!)

I'd invite you to carefully read the mails #RMS wrote back then. And then compare them with the accusations he got.

But the sad thing about lynching mobs is that no matter how evident are facts, they can't accept them.
Because accepting they (virtually, as true keyboard lions) lynched a man for what he said, would hurt to much their own opinion of themselves.

A lynching mob will never accept the victims' innocence, or their right to a due process, because otherwise they would have to accept to NOT be the rightful people they pretend to be.

@jz

@jz

I'd add #RMS lynching to the list.

@fudgel

Did you noticed your aggressive tone?

That's the usual approach of people supporting #CoC, #workplace like management (aka exploitation) of highly specialized #volunteer work, and #hacker marginalization.

I have no time for you. 😘

@ambrevar

@ambrevar

PS: I noticed you didn't signed such statement. I really appreciate it.

But still, your work is contributing to that same project. Even if you don't like it.

@ambrevar

I followed a bit the debate on the mailing list. But frankly, since it's still on the website and nobody published a "Joint Statement fix", #Guix last word is written down there.

I'm a #Debian #GNU #Linux user since "Potato", but after the #systemd outcome I was looking for an alternative.

I like some of the technical features of Guix / #Nix but honestly... I can't support a project joining the lynching of a man for what he _said_.

So in fact, all I can appreciate the concept, that "joint statement" really deter my usage of Guix.

#Software is a form of #expression.

#FreeSoftware IS #FreeSpeech.

I know there are #OpenSource people who pretend to ignore what happened and celebrate it like a #CoC success or so.

What I find very daunting is seeing this happening within #FSF and #GNU.

#Google is winning. 🤮

@snow

I have another idea. 😉

The "#trolley problem" is a trick to spread the idea that human lives can be priced.

It force people to accept to kill AND to give a comparable value to people.

Then the #MoralMachine from #MIT went on: what if you have to choose between the life of a kid and that of a executive? What if you have to choose between one pregnant woman and a homeless? What about a "criminal" or three dogs?

Human lives are not comparable.

Each person is unique: his value is not a scalar, but a vector orthogonal to the value of each other.

But the trolley problem has a simple and obvious solution: design and build safer tracks and trolleys, so that people CANNOT be killed.

Once you think about it, it's the obvious solution. And an optimal one.

Some will argue that such safe system is expensive, so you have to choose.

But guess what?

These are those who want to sell them. And those who want to sell #Capitalism. Because this is not, actually, #philosophy, but #politics.

@ambrevar

To be honest, since https://guix.gnu.org/blog/2019/joint-statement-on-the-gnu-project/ I feel uncomfortable with #Guix.

What I've read there and on https://freesw.org/ puzzles me.

Looks like #OpenSource that finally replaced #FreeSoftware inside the #FSF is attacking the #GNU movement, now.

@ohyran

I don't know where you studied #Latin, but "firmitas" had nothing to do with performance.

It's stability.

@xj9

@grainloom

Sounds very interesting, but consider you are trading read() time for lookup time.

With your fs, file lookup would be faster than in kernel as the kernel would have to try every bound package until it finds the desired program.

But then, each read will need to pass through your file server.

I don't think it would be a large overhead, but it would be linear to the number of reads.

It should also be noted that the #Plan9 kernel caches (for a while) .text pages from binaries, so this read-time overhead would probably be almost invariant on successive executions of a binary.

BUT scripts are not cached in kernel (they are text, after all), so such read-time overhead would be larger.

Also Plan9 memory page is 4096 bytes, so on a large binary the number of reads might be high.

@ekaitz_zarraga