Maybe to be more inclusive towards macOS or BSD users.

Automatic Semicolon Insertion (ASI) has (sadly) been a part of JavaScript longer than 2016. I’m not sure exactly when it was introduced, but this document from 2009 already contains it: https://web.archive.org/web/20120418215856/https://ecma262-5.com/ELS5_Section_7.htm#Section_7.9

IMO it’s bad practice to rely on ASI since the semicolons may not get inserted where you expected them to. The following snippet

const x = 0
const y = x
[1, 2, 3].forEach(console.log) 

is interpreted as

const x = 0;
const y = x[1, 2, 3].forEach(console.log);

which raises a TypeError.

There are more examples of ASI not doing the right thing on the web, so I don’t agree with “Javascript doesn’t need semicolon”.

Sometimes it does take a few seconds for me as well, but not even close to a full minute. That must’ve been on an HDD, right?

?

Sure, but in this case the bash prompt tells us that it’s located in the root directory.

The explanation is most likely incorrect though. A more obvious cause of this error is that the current working is the root directory (/) and that they’re logged in as a non-root user, thus trying to create the file /woman without sufficient permissions.

Nope, it can’t. You’ll have to continue using yt-dlp/youtube-dl for that. Both actually use ffmpeg to merge the downloaded audio and video streams into a single file.