Not just "subjectively extremely correct", the reader understanding your intention is the literal definition of communication.

The problem as a writer, though, is that you don't know if the "as long as" is going to hold. Punctuation as a set of rules that must be followed is certainly unhelpful nonsense, but punctuation as a tool to help point those who might be misdirected without it is worth some consideration.

As long as they create self-contained sentences, periods/full stops are always a safe option, so you shouldn't need to worry about using them in either of these instances.

Arguably the first comma example should be replaced. As it is, it's splicing two unconnected ideas. A semicolon may seem 'speedier' but I would (personally) avoid even that here since the two parts don't seem (to me, absent context) to be sufficiently tied together to validate that choice. In any case, if this is text for children, the punctuation should be simple, i.e., use a period. If the text is for adults, they shouldn't be assumed to be two-mississippi-ing after periods and, consequently, periods should not be seen as slowing them down. So... just use a period.

In the second example, if not a safe period, a colon is perfectly fine: the dialogue is directly related to the preceding text. A copy edit along the lines of:—

Lacing it with sarcasm, Maddie laughed, "Mark, looks like you’ve got a friend."

would justify the comma according to the style I've acquired, but that's a much bigger change for the sake of a comma.

It all comes down to taste though, so take my comments with a pinch of salt.

I assume you've read the Wikipedia article for Marxist film theory since that's the obvious search engine find, but have you also looked at Marxist literary criticism? That page breaks things down a bit more in the last section.

These tourist shows just keep getting better and better: thousands of background performers, full-scale, moveable train props; the "tunnel" background didn't even look like it was just a big cylinder going round and round outside the shaking carriage window. Just think what they could do if they put all that effort into building a proper market economy!

At 16:38–16:44, CEO killer confirmed as North Korean operative.

Yeah, that's what I was suspecting.

I ended up leaning towards "download" being used in the boomer way of meaning any data transfer, whatever the direction, which in this case would more specifically be called an "upload". And that "online" was being used to mean "using a website", even though the local processing is offline.

The alternative fit to the description I had considered was a website you could give an URL, so it retrieves the zip file and allows you to inspect it remotely, and maybe just download some of the contained files, so it deals with the risk and bandwidth issues for you. That would be a different kind of useful, though it'd only be a few days before someone uses it for malign purposes and gets the site operator a no-knock visit from the fuzz, so that seemed much less likely.

I can see a use for an app that can be used where they can't be installed, though.

I'm confused. How are you defining "download" and "online" here?

The website suggests that the server holds the files and does the extraction:

Extract and Explore compressed files online [emphasis mine]

which fits with the github claim of:

to view and extract zip files online without downloading them

but the website also states that:

nothing leave your browser

which suggests that the server has nothing to do with it, and you do actually download the zip files first.

What am I missing?

Didn't the UK try something like this over the last decade? How'd that work out? Did they get a good one at any point?

How do you issue a recall notice to a rat?

Right, so we can actually estimate this, if we have some faith in Zipf's Law as a model for character popularity, and assume that popularity will roughly follow total appearances.

The a and b parameters in 1/(rank+b)^a can't be entirely arbitrary, since the sum for the first 9 ranks—representing the main cast, each credited in over 100 episodes—should be plausible (probably over 90% of people's favourites). So adjustments to one necessitate changes to the other parameter. Playing around this way, we can look at the popularity of the 23rd most frequently appearing character, Kai/Vedek Winn (14 episodes).

Even assuming a lower rank, since the global audience for DS9 is at least 10 million, you need quite large values for a to create a model where not even one viewer regards Kai Winn as their favourite. Much lower ranks (small changes don't make much difference) are needed to change that.

Of course, whether anyone would actually admit to Winn being their favourite is another factor entirely.

You have to remember the puritanical roots of the country.

The upper/middle/lower class distinctions are not economic:

• upper = rich;
• middle = comfortable;
• lower = poor.

They're instead based on morality:

• upper = blessed;
• middle = virtuous strivers;
• lower = good-for-nothing work-shy losers.

The upper class have been divinely marked for better things. They are never helped. Everything they receive is ordained. The lower class are scum who it would be wrong to ever help, since it would only encourage their inherent unwillingness to work. The middle class, then, are the self-made people who work hard for what they get and obviously deserve a little more, which in self-image terms is basically everyone.

Politicians promising to help the middle class are, therefore, declaring that they will reward the worthy (and punish the unworthy), which is a popular sentiment.

Are there any art or maker groups in your area? If you can get to one (or more) of those, there are going to be people who will fall over themselves to talk to you if you just ask them about what they've made.

People love when someone shows an interest. You don't need to know anything (or pretend to know anything) beforehand, and the same few questions/prompts can be reused: from a vague "tell me about [the thing you made], to "what was the hardest part?", "how did you do this bit?", "did you learn anything cool along the way?", "what do you think you'll make next?" So long as your interest is genuine and you actually listen to what they say, you can't really mess things up.

And if you want to make anything yourself, regardless of your current abilities, such groups tend to be quite nurturing, where someone will show an interest in you too. Art in particular is an expressive pursuit that attracts lefty weirdos. The desire to connect with people is right there for you to be a part of.

Old contender:

𓁶

the intent of the code is to get the previous month RELATIVE to the current date.

But that isn't what it does. From the original post:

function getMonthName(monthNumber) {
  const date = new Date();
  date.setMonth(monthNumber - 1);

  return date.toLocaleString([], { month: 'long' });
}

That is a function which is meant to take a number (presumably 1 to 12) and return a localized name for it. This is essentially an array lookup and should return the same output for a given input (and locale) every time it is called. If the intent is to return a value relative to the current date, it is even more wrong, since it should gather the month from the current date, not the function paramenter. This claim of intent, not present in the original post, is an example of you changing your story over time.

Yes, it would help find the problem faster because the first time invalid date is passed in the program will crash.

No, it wouldn't. As I have said before, testing for unexpected return values is just as effective as testing for errors, that is, not very with the function originally presented under sensible assumptions. If the function actually did look like the intent you claim, the tests would be different, necessarily replacing Date for consistent runs, but would be equally likely to catch the problem whether failing on value or error. And if you are eschewing testing and relying on runtime crashes, you have bigger problems.

Given that I have agreed and commiserated, and neither of us can change JavaScript, there is nothing to be gained from pursuing this complaint. In contrast, what I have tried to say, if followed, would give you an approach that leads to more reliable code, even in the face of undesirable APIs.

I had thought that worth pursuing, and had thought you worth investing my considerable time. Alas, I can only lead you to the water...

I'm not missing your points, even as you change them. I've agreed that JS sucks. I've agreed that errors can be more helpful. I'm not trying to argue with you about that. What I have said, from the beginning, is that in the code you originally presented a behavioural change for setMonth will not help you find the problem any faster. Test failures for the wrong output occur just as often as test failures for errors, on exactly the same few days each year. The API change gives no advantage for the specific function this discussion started with in this regard. However, an approach that avoids inconsistency will, because in this particular instance, that is the real source of the problem. That is all.

In that context—the one you started with—it does not matter that there is often good reason to call Date() without arguments. The getMonthName function presented, effectively an array lookup, should produce the same output for any given input every time. It has no reason to engage in any behaviour that varies from day to day.

There is absolutely nothing wrong with getting the current date.

Bluntly, the code you presented fails precisely because it gets the current date where it should create a more specific one, and then fails to deal with that variation appropriately. You can keep distracting yourself with language design decisions, but that won't help you avoid this particular type of problem in the future because that's not where it is.

Getting the current date is often fine. In this specific instance, it is not. That is why the function doesn't work. If you are missing that point, as much as I appreciate your enthusiasm in continuing the conversation, I will take the L (and the code that actually works) and move on.

Yes, and I've said that I agree with that in general. I know that this isn't hypothetical; that's exactly why I keep saying that throwing an error doesn't help you find this bug early at all.

Even the silent weirdness can be caught by the most basic of tests checking output against input, but only if your function works the same way on every invocation.

Whether making a giant fuss (as you'd prefer) or making the best of it (as it actually does), the setMonth method always works the same way. My code always works the same way. The setDate suggestion makes the code always work the same way.

Code that always works the same way is easy to test.

If the day of the month is constant and incompatible with setMonth, whether there's a thrown error or just an unwanted return value, a simple test will reveal that on every test run. If the day of the month is constant and always compatible with setMonth, the test will pass appropriately on every test run.

The bug in the code you originally presented comes from working differently over time. That's why, most days, tests won't identify the problem, even with a fussy, noisy API. Most testing days, the date will just happen to be compatible, and even the fussiest, noisiest API will carry on without any mention of the problem.

The reason the original code works differently over time has nothing to do with the silent, unexpected behaviour of setMonth. It's entirely down to calling Date() without arguments, the entire point of which is to give different values over time. That call effectively introduces state that is not controlled by the function. And not bringing it under control is the real source of the bug.

Yes, absolutely, JavaScript sucks. Make F# the only supported web scripting language! But JavaScript's suckiness is not the cause of this particular bug. JavaScript's suckiness is not the reason this bug is hard to catch. The real problem lies in code that functions differently over time when it should (and could easily) be consistent. That's what actually makes it hard to test.

Plenty of other languages and API design choices still allow code that functions that work differently over time, which is why, as justifiable as the complaints are in general, those factors are irrelevant for this particular bug. Write code that always works the same way and the problem goes away. That's the real core of the issue.

Obviously, that's easier said than done, and it's irritating that neither loud errors nor most testing will help you in this regard, but that's the way it is.

I agree with you that errors are useful feedback for coders who don't know the ins and outs of an API. And every programmer is in that group at some point. But the difficulty in identifying this particular bug doesn't stem from the API decisions.

Whether Dates throw an error, or work with what they're given, has no bearing on the subtlety of this bug. Either way, tests that don't replace Date will fail to identify it most of the time, and tests that do, based on its use within the function, would be called wrong-headed by many.

Either way, the bug only shows up at the end of months longer than the target month, and that infrequency has nothing to do with the peculiar design choices of the Date API. It stems exclusively from the evaluation of Date() called with no arguments returning different values at different times—behaviour you have not objected to, and which I'd expect to be considered entirely appropriate, in fact its very point—combined with an attempt to use that value, whatever it may be, without due consideration.

Since the month is the only part of interest, there's no reason to allow the other parts to vary at all. Fixing them, as I suggested at the beginning of all this, is the simplest approach, but setting them first, as has also been suggested, would work too.

You can once again complain about JS design decisions and I'll agree about many of them, but, as much as you might like it to be, and as annoying as so many of us think they often are, here it is beside the point. The perniciousness of this particular bug stems from unnecessarily calling a function with inconsistent output and then improperly processing that, instead of using a function call with always-predictable output.

I've tried to point that out in all the ways I can think of, so if it's still not getting through, I give up. And if your acknowledgement was too subtle for my sleepy brain, and I've ended up overexplaining, then I'm sorry.

I was taught that side effects are not so one-sided, and that changing output in response to outside state (such as the date) is also a side effect, a side effect on the function, rather than a side effect of the function, but I'm happy to use other definitions so long as they're commonly understood.

As I said before, though, even if JavaScript did throw an error as you'd prefer, it would still allow your function to have date-based problems. They'd be a bit noisier perhaps but no less present, and just as "well it's worked fine so far". And that's because, as I keep saying, the real problem here is using a function with inconsistent output and not thoroughly dealing with the possibilities. An API change wouldn't alter that. Most of the time it would still let you write bad code.

I also probably agree with you that errors are generally better than silence in response to bad input but, as someone else has said (more or less) it's not always unreasonable to consider "31st [Month]" as 31 days after the end of [Previous Month]. Without throwing errors, this flexibility is possible. Perhaps the creators believed having to mutate the day-of-month first was an acceptable trade-off for that.

You've replied while I was editing, so see that regarding what I mean by side effects.

As far as throwing an error when you try to create "31st February", this wouldn't actually help much, since the error would still only occur on some days of the year, because your original code doesn't account for the range of outputs from Date() when called without arguments.

To perform correctly, your code needs to normalise the day of the month, or just create the date more explicitly to begin with, but this is a calendrical issue, not a JavaScript one.

The rake has nothing to do with JS (which I agree is cursed, but for its own reasons, not this).

You have called a function in a way that does not give a consistent value (Date()). Such functions are hardly the preserve of JavaScript. You've failed to adequately deal with the range of values produced, with code that tries to insist that the "31st February" can be a meaningful date in February. You should accept that this is your mistake and learn to (better) avoid side effects where possible.

Also, the function isn't side effecty since it doesn't make implicit references outside its scope.

Edit responding to your edit:

Also, the function isn't side effecty since it doesn't make implicit references outside its scope.

The Date() function's output varies according to something other than its input (and even the rest of your program). Using its output without accounting for that variation means that your function, as originally written, also gives inconsistent return values, varying according to something other than its input, because it does, in fact, reference something outside the function. If it did not, the results would only depend on the monthNumber argument, and would always be consistent. I don't know what you call that, but I view it as a side effect.

As you have said, the rake is that months have different lengths, and you need to account for that. But that's not one of JavaScript's many issues.

You want to create the date "31st February", but it's JavaScript that's cursed?

Write a less side-effecty function.

function getMonthName(monthNumber) {
    const date = new Date(2023, monthNumber - 1, 1);
    return date.toLocaleString([], { month: 'long' });
}