Jump in the discussion.

No email address required.

This is why the Jeets are saying they are women so we can finally get rid of the mayo foid menace in tech.

Jump in the discussion.

No email address required.

I never thought I'd die fighting side by side with 'jeet

:chudconcerned#talking:

What about side by side with a chud?

:marseychudindian#talking!:

Aye, I could do that

:chudsmugtalking#:

!chuds !codecels

Jump in the discussion.

No email address required.

im never gonna get over that grace hopper womens job conference that got swarmed by indian dudes last year

Jump in the discussion.

No email address required.

Funny thing is no one could answer how they knew those were dudes. I mean, if they identified as women then they're women, right?

Jump in the discussion.

No email address required.

They live by the truth of their choice

Jump in the discussion.

No email address required.

Foids deserve it.

Jump in the discussion.

No email address required.

All right lets see what a "feminist programmer" looks like

https://i.rdrama.net/images/1729820017554114.webp

Jump in the discussion.

No email address required.

https://i.rdrama.net/images/17304410696952393.webp

Astounding

Jump in the discussion.

No email address required.

https://media.tenor.com/CHPYI0uQIi8AAAAx/austin-powers-mole.webp

Jump in the discussion.

No email address required.

Error messages are mean!

:marseysob:

A reviewer didn't take my paper seriously!

:marseysulk:

Why are there papers on feminism in programming I haven't read!

:marseycrying:

The work I do isn't aligned with the focus of the conferences and publications I want to publish in!

Then publish in HCI conferences!

Over time though, me and the PL community parted ways, and I drifted

REEEEEEEE Get an editor!

You give women in CS a bad name!


Why are there two authors while the entire piece is in the first person?!

AAAAHHHHH FOOTNOTES ARE AT THE END :marseyschizotwitch:


Take away: This isn't a paper, this is an opinion piece.

Jump in the discussion.

No email address required.

Error messages in many languages explicitly do not include the user in their phrasing, saying things like 'missing bracket' or 'unknown variable', which leaves the user out of the equation. For a person with the lived experience of being told they don't belong in programming and being afraid of failure in the programming world (a common experience for women in computing), unclear or unhelpful error messages are more likely to have negative impacts.

So much this. GCC error messages keep triggering my unresolved mommy :marseyaoc: issues.

Instead of a short and concise error message that is quick and easy to parse, the compiler to should output an essay :marseykernelpanic: on how it feels, but it won't tell you what's wrong until you interrogate it enough :marseygossip: and correctly, and drink a calming herbal tea. :marseycoffee:

More readable error messages are not just helpful for those with less prior knowledge, clear error messages are a better experience and will help all users—even professional developers.

This is a feel-good recommendation. Error messages with more context or counter-examples will likely drive up compiler complexity and development effort. Keep in mind, the antecedent of this sentence is "error messages are not inclusive." I think is just some weak justification of the "PLs are exclusionary" header.

I had never realized before I started to work in localized PL design, that this does not include all people's experiences! In Arabic, digits are not 0-9 but 0..9.5 These numerals are not included in most programming languages, creating a situation in which none of the languages in the TIOBE top 10 6 can be used to calculate 1 + 1 (1+1) in Arabic (or in the dozens of other numerals around the world)

No consideration for why we have a lingua franca, or the benefits of having it.

We see this paper as an invitation to everyone in the programming languages field to deepen our collective understanding of the forces shaping our field

Chesterton's Fence. This paper is more an amalgamation of complaints than an exploration of the subject. At least, at the end they do remark that the paper is an aggregate of research directions and an index of (hopefully, more insightful) papers.

The current standards of evaluation in the PL community are set from a masculine perspective as well, valuing formalism and formal methods over user studies, quantitative over qualitative work, and the examining of technical aspects over context and people.

Bondage and discipline languages are more masculine. This means that Rust programmers are the manliest programmers :marseybuff: of us all

Jump in the discussion.

No email address required.

Error messages in many languages explicitly do not include the user in their phrasing, saying things like 'missing bracket' or 'unknown variable', which leaves the user out of the equation.

Wouldn't this make error messages sound more accusatory?

Jump in the discussion.

No email address required.

also what if the error appears in code you havent written? did she think about this for over 5 seconds :marseybruh2:

Jump in the discussion.

No email address required.

what if the error appears in code you havent written?

:marseyme#:

Jump in the discussion.

No email address required.

Message before: "Error: Missing bracket in line 765"

Improved feminist message: "You fricking waste of oxygen. You've missed a bracket somewhere like a r-slur. Frankly the best part of you rolled dowm your mother's leg"

Jump in the discussion.

No email address required.

this is so incredibly long

Jump in the discussion.

No email address required.

I tried to read the paper and it's just too straggy

Jump in the discussion.

No email address required.

Not reading al that. here's a summary by ChatGPT

The paper, "A Case for Feminism in Programming Language Design" by Felienne Hermans and Ari Schlesinger, presents feminism as a lens to analyze programming languages and their design. It addresses two key issues: the persistent lack of diversity in the programming language community and how dominant intellectual norms have shaped programming languages. By using a feminist perspective, the authors argue that this can help us understand the exclusion of marginalized groups and offer insights into making programming languages more inclusive.

Key points from the paper include:

1. Intellectual and Cultural Norms: The paper argues that programming languages are predominantly designed by men, which reflects masculine priorities such as formalism and quantitative analysis over user-centered or qualitative approaches. This marginalizes research and design that focuses on people and social impacts.

2. Feminism as a Framework: Feminism can challenge the male-dominated values in the field and question why certain aspects of language design are prioritized. The focus on "hard" or technical problems is seen as masculine, which undervalues work that focuses on usability, accessibility, or inclusivity.

3. Barriers to Inclusion: The paper outlines how the standards of evaluation in programming language research often exclude work that isn't seen as difficult enough or aligned with traditional quantitative methods. This limits diversity both in research topics and community demographics.

4. Expanding Diversity: By encouraging diverse intellectual and social practices, the authors aim to foster a programming language community that is more welcoming to different identities and perspectives. This includes addressing issues such as accessibility, error messages, and the exclusion of non-English and non-Western numerals from programming languages.

5. Historical Context: The paper also highlights the historical exclusion of women from the field, despite their foundational contributions, and how this has shaped the current gender imbalance in programming language research.

In summary, the paper advocates for a rethinking of how programming languages are designed and studied, calling for greater inclusion of marginalized perspectives to enhance the field's intellectual diversity.

Jump in the discussion.

No email address required.

not reading al that. Here's a summary of chatgpt's summary

The paper "A Case for Feminism in Programming Language Design" uses a feminist perspective to critique how programming languages are designed, highlighting the lack of diversity in the field. It argues that dominant masculine norms, such as prioritizing formalism and technical difficulty, exclude marginalized groups and user-focused approaches. The authors advocate for more inclusive practices in programming language design and research, aiming to broaden participation and consider diverse perspectives to make the field more accessible and equitable.

Jump in the discussion.

No email address required.

not reading al that. Here's a summary of chatgpt's summary of chatgpt's summary

The paper argues that programming language design is shaped by masculine norms, which limits diversity. It calls for more inclusive practices to make the field accessible to marginalized groups by valuing user-focused and diverse perspectives.

Jump in the discussion.

No email address required.

tldr

Jump in the discussion.

No email address required.

kill men

Jump in the discussion.

No email address required.

Programming is too hard for me and that makes me feel bad

Jump in the discussion.

No email address required.

"more accessible" basically just means "make it easier for women and BIPOCs because they're too dumb to get it :marseyretard2:

Jump in the discussion.

No email address required.

Anyone who can't understand object oriented definitely can't rotate a photorealistic apple in they head

Jump in the discussion.

No email address required.

All those words won't bring daddy back.

Jump in the discussion.

No email address required.

glad someone else is trolling the lobster traps. :marseylobster:

Jump in the discussion.

No email address required.

Women don't go into programming they go into women in programming.

Jump in the discussion.

No email address required.

Computers went to shit when they started making them for BIPOCs.

Snapshots:

https://www.felienne.com/archives/8470:

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.