Disaster Richard Stallman resigns from the Free Software Foundation and his position at the MIT

RMS has resigned from some honorary position at MIT.

To the MIT community,
I am resigning effective immediately from my position in CSAIL at MIT. I am doing this due to pressure on MIT and me over a series of misunderstandings and mischaracterizations.
Richard Stallman
Vice Article
 
FOSS needs a Pinochet (a Hitler would also work), and it needed him about five years ago.
Dictators like them are anathema to the fundamental principles of free software. If the community was willing to abide such autocratic figures, we'd all be running the GNU OS rms tried to create with this exact methodology. Read Hackers.
 
Dictators like them are anathema to the fundamental principles of free software. If the community was willing to abide such autocratic figures, we'd all be running the GNU OS rms tried to create with this exact methodology. Read Hackers.

I understand the hacker ethos, as do you. However the big problem is that a growing number of contributors not only don't understand it, but see it as an oppresive force because it doesn't seek to push their agenda.

While authoritarianism is not a good tool to push back against itself, what is a good tool is exclusion. That is what I meant, in an edgier way when I mentioned Pinochet and Hitler.

It's okay, and even good to be inclusive. But you can't just include anyone, or else you'll just get crap like the image I quouted before and worse. It wouldn't be as much of a problem if these same people didn't demand that all the people that do/did put work into their projects be ousted for minor slights that would offend no normal person.

A little bit of a purge of those that refuse to assimilate just might be what the FOSS community (and likely communities in general) needs from time to time. It's not ideal, but neither is the current situation.
 
Repent you sinners! Thou shalt not shun vim over emacs! The inclusion of e-mail agent and web browser in a "text editor" is an abomination in the face of the Lord and one of the main reasons we've been forsaken by the God.
Picking Lisp for his text editor was a far more intelligent choice than picking UNIX for his operating system. If he'd built his entire operating system on Lisp, the world might not be in such an embarrassing place as it is in terms of software.

But hey. It's better than Windows, right?
Emacs is not a text editor. It's a lisp machine emulator with a textual interface. It allows it to be a text editor, yes, but also to manage processes and to be programmed in its own language and environment. It isn't that lisp was picked, it was the only option. And given that it's an emulator.
I don't know how well an OS written in any lisp would do. There's an experimental OS written in CL and it's nice but old lisps have a few issues which either make them very pretty but not too useful (scheme) or a monstrosity designed by a committee (CL). I like Clojure because it innovates on many ideas in lisp, but you aren't going to do systems programming in a JVM language. Maybe when it's ported to C.

I understand the hacker ethos, as do you. However the big problem is that a growing number of contributors not only don't understand it, but see it as an oppresive force because it doesn't seek to push their agenda.

While authoritarianism is not a good tool to push back against itself, what is a good tool is exclusion. That is what I meant, in an edgier way when I mentioned Pinochet and Hitler.

It's okay, and even good to be inclusive. But you can't just include anyone, or else you'll just get crap like the image I quouted before and worse. It wouldn't be as much of a problem if these same people didn't demand that all the people that do/did put work into their projects be ousted for minor slights that would offend no normal person.

A little bit of a purge of those that refuse to assimilate just might be what the FOSS community (and likely communities in general) needs from time to time. It's not ideal, but neither is the current situation.
If you think about it, Linus and RMS are (were) dictators of their own domain, but are benevolent dictators, happy to let their folks do their own thing, but happy to slap someone down if they do something stupid and their word is law. If Linus rejects your PR, it's not getting in. Same for your patches to GCC and RMS.
 
Doesn't the Windows 10 BSOD have a fucking smiley on it now too?
Yep!
windows10bsod.png

I was actually morbidly curious about this, so I did some digging. Seems to be fake, un/fortunately. The miku-chan03 github account didn't join the site until April 2018 apparently, and has no other activity since. The one in your screenshot might have deleted their account earlier perhaps, but I can't seem to find that issue ticket either. (It'd still appear in gaearon's issue tracker, right? Since miku-chan03 is the one asking for a merge, despite apparently also being a Contributor...)

It did lead me to this mostly empty MikuChan03 github account that joined later in May 2018, with the same profile pic and the same obnoxious commenting style:
absolutelyobnoxious.png

But whether or not that's even the same person and not a copycat, I'm pretty sure they're just having a laugh at this point.
 
If you are ever in a position of power, never hire or associate with women or men pretending to be women. I cannot overstate how inadequate they are for software development and how dangerous they are to your personal reputation and livelihood.

I don't see why women who genuinely want to work for software development can't be hired or get the job they really want because of this.

Seriously, anyone who thinks it's good to screw over all the women who do want to do the hard work because other women are dangerous should never make important decisions.
 
Q.E.D., Andrew Chael writes almost a million lines of code to photograph a blackhole and a cute undergrad student named Katie Bouman who mostly did user interface work gets the credit from the MSM (outside of China).
View attachment 938480
That may also be a general problem with people's understanding of what's impressive and smart in tech. How many know this sort of story:

CEO: "The guys in the basement have made some changes so we can serve the new batch of incoming users without buying ten times as many instances. But the real news: those front-end wizards have done it again! Look at this icon! SPINNY!"
 
CEO: "The guys in the basement have made some changes so we can serve the new batch of incoming users without buying ten times as many instances. But the real news: those front-end wizards have done it again! Look at this icon! SPINNY!"
No. If the woman had written the actual logic of the software she'd end up a poster child of the industry like this.

1568966913899.png
 
I was actually morbidly curious about this, so I did some digging. Seems to be fake, un/fortunately.

It may be fake, but I shit you not that's a REAL glimpse into the future.
FOSS won't die from screeching trannies, it's far-right pushback, or autists shitting all over the code.
It's death knell will be the day it's completely consumed by "huggie wuggies uWu".
 
Q.E.D., Andrew Chael writes almost a million lines of code to photograph a blackhole and a cute undergrad student named Katie Bouman who mostly did user interface work gets the credit from the MSM (outside of China).
That may also be a general problem with people's understanding of what's impressive and smart in tech. How many know this sort of story:

CEO: "The guys in the basement have made some changes so we can serve the new batch of incoming users without buying ten times as many instances. But the real news: those front-end wizards have done it again! Look at this icon! SPINNY!"
No. If the woman had written the actual logic of the software she'd end up a poster child of the industry like this.
All of this discussion inspired me to do another dive into that whole black hole imaging thing. After all, everything's online right? All of the components of the imaging project are public: the journal article detailing the black hole imaging, the two imaging software libraries used for the research, and the many ancillary articles further detailing the methodologies used. Assigning credit where credit's due ought to be straightforward.

Short version: Everybody got fucked by the media on this one. @Null was right about Andrew Chael losing due credit for writing most of the useful code. But at the same time, since she was given undue credit in writing the code, nobody cares about the work that Katie Bouman apparently did do (so @OwO What's This? was right too: it often sucks just as much for women). People barely even care who Michael Johnson is, even though he was also important in the project. And the Japanese team working with Kazunori Akiyama didn't get any credit from the media at all, poor guys.

Andrew Chael got fucked. It absolutely appears that Chael wrote most of the useful code in the eht-imaging codebase (though Michael Johnson made some significant contributions too). The visual comparison of the github contributions in that image Null posted suggests this to be the case, but what if most of his commits were boilerplate stuff? Well, we can note that he's first author on the papers that describe how the eht-imaging algorithm works. Importantly, that paper of his from 2016 develops most of what they essentially use for the black hole imaging, which means that by 2016 the eht-imaging code is mostly operational. (Snapshot from the 2016 article: )
ehtimaging.png

In other words, a full two years before Katie Bouman contributes her first 'line of code' to the repo.

Katie Bouman got fucked. First off, since the media can't seem to decide on what her credentials are (is she undergrad? is she a postgraduate student?), let's settle that now: she's a full-fledged Postdoc Researcher. Here's her PhD thesis submitted back in 2017, on the topic of computational methods for imaging black holes. Further, she has an impressive CV of published articles related to computational imaging and machine learning, many of which she appears as first author on (in particular, this paper of hers on VLBI is very relevant for the black hole imaging). In all likelihood, while she may not have done much of the coding, she probably still contributed a great deal of subject-matter expertise during the research.

Kazunori Akiyama (and friends) got fucked. Who? Exactly. These guys independently wrote the SMILI code that was used in the black hole imaging project to produce a second set of black hole images to compare/contrast with the ones from the eht-imaging team. The two results validate each others' work, were produced at the same time, and look equally impressive:
blackholes.jpg

But the mainstream media didn't even mention them.

And probably many others got fucked. I mentioned Michael Johnson earlier: he's second coauthor on pretty much every paper in the project, and contributed useful code to the eht-imaging library. Also, the list of authors for the journal article has hundreds of names on it. Now many of them probably didn't even contribute to the project (it's a well-known meme that Physics departments inflate authors lists by adding literally anyone who so much as stepped foot in the lab during the research). But as @cecograph hinted at, there's bound to be some more people in the list who had critical contributions, but that nobody cares about because they aren't project lead/the cute woman/the gay guy.
 
I don't see why women who genuinely want to work for software development can't be hired or get the job they really want because of this.

Seriously, anyone who thinks it's good to screw over all the women who do want to do the hard work because other women are dangerous should never make important decisions.
I'll tell you why, and it's the sad reality of differences in behavior and psychology between the sexes: women have higher in group preference than men do. No matter how talented and sharp they are, unless they are too autistic to look anyone in the eye they will prefer women in hiring and they will bring in the fifth columnists into your organization. They can't help themselves.
Based on talks with women I work with. They all get stupid when other women are involved.
 
  • Informative
Reactions: frozenrunner
I understand the hacker ethos, as do you. However the big problem is that a growing number of contributors not only don't understand it, but see it as an oppresive force because it doesn't seek to push their agenda.

While authoritarianism is not a good tool to push back against itself, what is a good tool is exclusion. That is what I meant, in an edgier way when I mentioned Pinochet and Hitler.

It's okay, and even good to be inclusive. But you can't just include anyone, or else you'll just get crap like the image I quouted before and worse. It wouldn't be as much of a problem if these same people didn't demand that all the people that do/did put work into their projects be ousted for minor slights that would offend no normal person.

A little bit of a purge of those that refuse to assimilate just might be what the FOSS community (and likely communities in general) needs from time to time. It's not ideal, but neither is the current situation.
Good luck with that, especially in the age of collaboration platforms like Github. However a good way of avoiding many problems is, and may esr have mercy on my soul for saying this, the cathedral model of software development. The bazaar allowed for participation of way too many agenda-pushing entryists and is what I blame directly for the ridiculous amount of bloat and idiotic meme solutions prevalent in modern FLOSS.
 
Didn't we have a thread last week dogpiling RMS for defending pedophilia?

It's fun watching the cognitive dissonance this situation is throwing up for some people
>fuck RMS for expressing a nuanced opinion on a topic *I* find taboo
or
>fuck SJWs for destroying people who express nuanced opinions on topics *they* find taboo
:story:

Picking Lisp for his text editor was a far more intelligent choice than picking UNIX for his operating system.
The goal was the write a non-Unix kernel too (GNU Herd) but in the early 90s it wasn't ready yet and the sudden arrival of lawsuits against BSD threaten to destroy the only usable open source OS. The plan was to back Linux only until Herd was ready.

If he'd built his entire operating system on Lisp, the world might not be in such an embarrassing place as it is in terms of software.
The two things Lisp had going for it is homoiconic syntax and dynamic typing.

The former makes metaprogramming easier and was memed to be the key to artificial intelligence but lead to the 1980s AI Winter when people realized there's a bit more to it than that.

Dynamic typing is lisp's lasting legacy passed on to all those hacky user friendly "scripting" languages, Python, Javascript, Lua etc. because it is faster to hack things together and make changes to a program when there isn't a compiler trying to ensure there is a basic level of sanity.

It's difficult to get any level of robustness from applications like that though, without writing a unit test for every line of code, checking tons of things any staticly typed language would guarantee for free.

Note that Emacs isn't even 100% lisp, the important parts are written in C.
No one writes flight control software in Lisp (or Python, JS whatever) for the same reason they don't duck tape the wings onto the plane.

The reason we are drowning in a world of shitty software is purely economics. Although you could argue it's Lisp's fault that shit software is so easy and cheap to write.
 
I'll tell you why, and it's the sad reality of differences in behavior and psychology between the sexes: women have higher in group preference than men do. No matter how talented and sharp they are, unless they are too autistic to look anyone in the eye they will prefer women in hiring and they will bring in the fifth columnists into your organization. They can't help themselves.
Based on talks with women I work with. They all get stupid when other women are involved.
Do you realize how stupid it sounds to make blanket assertions based on anecdotal evidence?
 
The goal was the write a non-Unix kernel too (GNU Herd) but in the early 90s it wasn't ready yet and the sudden arrival of lawsuits against BSD threaten to destroy the only usable open source OS. The plan was to back Linux only until Herd was ready.
The choice of kernel has nothing to do with UNIX (Posix) compliance. Posix compliance is guaranteed in userspace by things like coreutils. GNU/Hurd would have been as much UNIX as GNU/Linux.

No one writes flight control software in Lisp (or Python, JS whatever) for the same reason they don't duck tape the wings onto the plane.
That's got nothing to do with typing. You write flight control software with hard realtime constraints in C because you can write code with extremely deterministic resource use, while in Lisp you might find you're pausing for a garbage collection in an emergency.

C isn't used because of its type system, because C's type system barely exists, and you happily cast between void*. Worse, it has no safety in its memory model. When you fuck up, the specification says that the behaviour is undefined, so good luck with not literally crashing.
 
That's got nothing to do with typing. You write flight control software with hard realtime constraints in C because you can write code with extremely deterministic resource use, while in Lisp you might find you're pausing for a garbage collection in an emergency.
Given Boeing's attitude towards passenger and crew safety, the main reason that their flight control software isn't written in Lisp is that no Indians know it.
 
Didn't we have a thread last week dogpiling RMS for defending pedophilia?

It's fun watching the cognitive dissonance this situation is throwing up for some people
>fuck RMS for expressing a nuanced opinion on a topic *I* find taboo
or
>fuck SJWs for destroying people who express nuanced opinions on topics *they* find taboo

We didn't completely destroy his life for it, we just made fun of him for being completely autistic.
 
Do you realize how stupid it sounds to make blanket assertions based on anecdotal evidence?
yeah, but the important part isn't anecdotal:
Four experiments confirmed that women’s automatic in-group bias is remarkably stronger than men’s
and investigated explanations for this sex difference, derived from potential sources of implicit attitudes
(L. A. Rudman, 2004). In Experiment 1, only women (not men) showed cognitive balance among
in-group bias, identity, and self-esteem (A. G. Greenwald et al., 2002), revealing that men lack a
mechanism that bolsters automatic own group preference. Experiments 2 and 3 found pro-female bias to
the extent that participants automatically favored their mothers over their fathers or associated male
gender with violence, suggesting that maternal bonding and male intimidation influence gender attitudes.
Experiment 4 showed that for sexually experienced men, the more positive their attitude was toward sex,
the more they implicitly favored women. In concert, the findings help to explain sex differences in
automatic in-group bias and underscore the uniqueness of gender for intergroup relations theorists.
The anecdote was relating to conversations I had with women who I consider quite talented and competent in their field. Your claim is basically NAWALT, so give one who's trustworthy and won't give me shit about SheCodes or hiring more wamenses.

No one writes flight control software in Lisp (or Python, JS whatever) for the same reason they don't duck tape the wings onto the plane.
unless some madman manages to program your satellite in lisp (there's an old one still flying around, some time ago nasa was hiring a lisp programmer for it)

It's difficult to get any level of robustness from applications like that though, without writing a unit test for every line of code, checking tons of things any staticly typed language would guarantee for free.
You know what's interesting about every bug in software that was written in a strongly typed language? It passed the type checker and compiled. Types don't assure correctness, they're guard rails against total idiots. There are several ways to overcome that with dynamically typed languages, in particular lisps, such as record types, schema enforcement at critical points in the system, polymorphism on demand, and racket also developed an optional type system which was ported to clojure. a real type system on top of your lisp. (to be fair circlci dropped core.typed, but they moved to schema).

The reason we are drowning in a world of shitty software is purely economics. Although you could argue it's Lisp's fault that shit software is so easy and cheap to write.
It really do be like it is. a bunch of code monkeys doing the needful, which can be thrown at a problem en-masse. I don't know if you know how much it sucks to interview people, and to have such high expectations of people with a good degree, good grades, experience, who can't solve fizzbuzz in any way other than the trivial. The sad reality is that good programmers and engineers are hard to come by, most are just okay.
 
Back