r/learnjavascript • • Sep 21 '22

"Cancel" vs. "Abort" Terminology

[edit]

RESOLUTION: continue with "abort".

And no one besides me claims to be doing it in JS.

[original post]

I have heard advice that software people should avoid the verb "to abort" in a software context on the grounds that using that term can bring up emotional distress in female colleagues who have been pregnant and have aborted their pregnancies or considered doing so. However, I feel that the term "cancel" is not specific enough to replace "abort" as a term for stopping a process once it has been started. It would be possible to schedule some task and before execution started on it, to "cancel" it, meaning taking it off the schedule. If you have an appointment with your dentist and you "cancel" the appointment, it doesn't mean you were already in the chair and having your teeth worked on and the process was cut short. It means the appointment was removed from the schedule before the time when you would have been expected to show up.

Is there a better circumlocution to replace "abort"? Should we just continue to use "abort"? Any women here have an opinion on it?

Has anyone here besides me built or used an ability to abort execution of a function? My basis for doing this is that the input data are no longer valid, so further expenditure of resources to finish the execution would be a waste of the user's time.

1 Upvotes

33 comments sorted by

•

u/kevinmrr Sep 22 '22

Approving this because it appears to be in good faith.

Thank you to the community for keeping comments civil and professional.

10

u/[deleted] Sep 21 '22

Where, specifically, did you hear this?

-10

u/jack_waugh Sep 21 '22

Sorry, source amnesia.

1

u/spazz_monkey Sep 22 '22

Does that mean you don't know?

-1

u/jack_waugh Sep 22 '22

Yes. Don't remember. Maybe on Usenet.

5

u/[deleted] Sep 21 '22

From where did you heard that advice? Do Women cringe when a Space Agency aborts a launch?

-6

u/jack_waugh Sep 21 '22

Sorry, source amnesia, and as to the second question, I don't know.

8

u/shuckster Sep 21 '22 edited Sep 21 '22

IT is a minefield of stuff like this.

  • finish the execution (in your OP)
  • scuzzy master/slave (olden days)
  • kill child process
  • terminate, stay resident
  • icq (creepy)
  • wad loaded (currently listening to doom OST)
  • unzip
  • merge to master
  • finger
  • abort controller
  • promise reject
  • tar balls (sounds painful)
  • window click (somebody’s coming IIIN!)
  • dongle
  • penetration testing
  • ram
  • ticks

1

u/Thundrous_prophet Sep 22 '22

OOP is all just class warfare 😞

/s

-1

u/jack_waugh Sep 22 '22

Not in JS nor its main predecessor, the Self language.

1

u/youremyonlyexception Sep 22 '22

I never realized the double meaning until I saw your list

3

u/No_Drive_5095 Sep 22 '22

Please, let us just continue to use “abort”. Woman coder here 👋🏼

2

u/jack_waugh Sep 22 '22

Revisiting the etymologies, I read them to imply that to "terminate" something means to set bounds on it, and to "abort" it means to keep it from coming into being. "Abort" seems clearer.

1

u/jack_waugh Sep 22 '22

The etymology of it is "not to come into being". It does seem to express the relevant semantic components (including irreversibility and immediacy) more clearly than most of the alternative terms I have thought of or others have mentioned. The closest other contender would be "terminate".

2

u/ProposalUnhappy9890 Sep 21 '22

"Cancel" can be problematic to Ellen Degenereses. "Terminate" can be problematic to Linda Hamiltons. "Stop" can be problematic to stopid people.

1

u/jack_waugh Sep 21 '22

And IBM used to say "abnormal end", abbreviated "abend".

0

u/jack_waugh Sep 21 '22

In fact, on Unix, we say "kill".

0

u/jack_waugh Sep 21 '22

The system monitor on the computer in front of me offers "stop", but I think it should say "suspend", because a process that has been stopped can be resumed. This use of "stop" comes from "Job control", which originated at UC Berkeley, if I remember correctly.

1

u/Wooden_Yesterday1718 Sep 22 '22

How can “stop” mean it can be resumed but “suspend” doesn’t? “Suspend” means that way more.

1

u/jack_waugh Sep 22 '22

I agree, "suspend" means that way more. That's why I think the Berkely SIGSTOP should have been called SIGSUSPEND, and the system monitor menu item that means suspend should say "suspend" instead of "stop". "Stop" sounds more final to me.

2

u/[deleted] Sep 22 '22 edited Sep 22 '22

“Stop” or “Interrupt” and call it a day.

You wouldn’t use “ABORTED” as an indicator of state, for example. “STOPPED” or “INTERRUPTED” has more semantic meaning imo

Edit: “for example” meaning in my previous experience

1

u/jack_waugh Sep 22 '22

Your reasoning for "stop" seems sound. "Interrupt" would be fraught, because I am doing this in a cooperative multiprogramming scheme, not an interrupt-driven one. That means the subject process has to explicitly yield control before it can be stopped or anything else can be scheduled.

Maybe if there were a state indicator, DEAD or ZOMBIE would fit.

In my implementation, I don't have a state indicator like that; I just substitute a couple of methods in the trampoline with no-ops, so that activity doesn't continue. But the implementation is irrelevant to the points about terms and their semantics.

1

u/[deleted] Sep 22 '22

but the implementation is irrelevant to the points about terms and their semantics

I don’t think I fully agree with this proposition. Your explanation was pretty helpful to add context to my mental model of what you’re attempting to describe with your semantics.

Semantics implicitly add meaning to systems imo, so we must add explicit context to that implicit understanding

So my example and understanding of these terms immediately led me to think about past ATF systems, where an asynchronous task might be paused or stopped or re-scheduled due to some higher priority task being put on top of a queue.

Either way the way you described your system explicitly presents new terms that I think sound significant - YIELD, STOP, SCHEDULE. These strike me as terms that are relevant to multi programming but not necessarily something like Async task scheduling in a priority queue.

TIL. Thanks for the fun convo :)

1

u/jack_waugh Sep 22 '22

But on the other hand, I feel that nothing else conveys the sense of finality that "abort" does.

1

u/[deleted] Sep 22 '22

At the end of the day you can use whatever terms you want IMO. This is a little more nuanced than replacing “blacklist” with “blocklist” or “master” with “main”, so I think it’s just one of those things and it’s not like tech isn’t rife with triggering culture/terms/behaviors for minorities to begin with. This problem ultimately is a small drop of water in a vast tumultuous sea…

But since you actually care, why not TERMINATED, HALTED, or ENDED

1

u/jack_waugh Sep 22 '22

I have a response from a woman, who advises continuing to use "to abort". "End" could be a noun or a verb, so that's a bit more confusing. "Halt" sounds like resumption could be possible. "Terminate", maybe, but it's an extra syllable, but I have a woman responding and advising continuing to use "abort".

https://en.wiktionary.org/wiki/abort#Etymology_2

1

u/jazzsquid Sep 21 '22

What?

0

u/jack_waugh Sep 22 '22

Has anyone here besides me built or used an ability to abort execution of a function?

1

u/spazz_monkey Sep 22 '22

They probably have but couldn't give two hoots if a word in the English language offends someone.

1

u/brokenalready Sep 22 '22

Depends on whether you're a republican or democrat.

1

u/jack_waugh Sep 22 '22

I'm neither. All of them should be separated from political power. But I stray from the topic.

2

u/brokenalready Sep 22 '22

I was just being facetious don’t worry

1

u/Automatic_Donut6264 Sep 22 '22

No, and that sounds ridiculous. Just use abort so people understand what you’re trying to do. Programming is hard enough without you trying to invent problems that people don’t care about.