• 1 Post
  • 128 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle












  • Well… The circumstances were that he was asked to whip up a little scripting language, that felt a little like Java and a little like Scheme, which could be used to add simple manipulations and interactions to web pages. Specifically to web pages. Not webservers, mobile apps, databases, banking systems, physics simulations, robotics… Only web pages. And nobody had even conceived yet of something like Google Sheets-- It was simple HTML forms and DOM manipulation.

    IMO in that context, it makes alot of sense. I think it was probably still the wrong decision-- definitely with the benefit of hindsight, and quite possibly even at the time, even in that narrow context. Way more trouble than it’s worth.

    But it’s beneficial to know that there was a principled (if misguided) reason behind it, that ties into the nature and history of the language-- It’s not simply “dude was in a hurry and not thinking.” Both are kinda true, but the former perspective helps us understand something useful, whereas the latter doesn’t get us anywhere interesting.


  • I mean, do you think that has more explanatory power though? The type coercion rules are actually more elaborate with == than necessary for equality checking, because it was intended as a clever convenience for working with strings. If it was really all about the short timeline, wouldn’t you just skip that and do a more straightforward equality comparison, like the algorithm that === implements?

    Besides, it’s not like everything in the language was conceived and implemented in those 10 days. The language has been evolving steadily since then. I’m not even sure if the modern == comparison algorithm worked that way in the first iteration.

    Personally, I find it more useful to understand the context that lets me say “that’s a quirky consequence of a sensible principle,” rather than blaming it on the “ten days” legend generically.







  • I did not know that. I believe you, but that seems like a pretty strange word to use. I couldn’t find any references to it online, either… I wonder if it’s colloquial.

    EDIT: I did manage to find some references to the phrase with a little more digging. I wasn’t getting far with “anger” or “in anger,” but the phrase “fire in anger” started leading to some interesting results.

    Dictionaries - MW and Dictionary.com don’t contain the phrase “fire in anger” or “in anger,” and their entries for “anger” don’t support this usage. Oxford has an entry for “in anger,” which just means “when angry.”

    Cambridge Dictionary’s entry for “anger” doesn’t support this use either, but it does contain the phrase “in anger” per se, which notes that the phrase is a) primarily in UK English, and b) is considered an idiom… i.e. not an ordinary use of the word “anger.” Interestingly, it doesn’t mention the military context, and uses examples (mostly) unrelated to warfighting.

    Wiktionary contains “fire in anger” (but not “in anger”). It’s described as a military idiom consistent with the usage in OP’s article. It doesn’t suggest usage outside of that context.

    Etymology - I can’t find any compelling etymology of “fire in anger” or Cambridge’s idiomatic sense of “in anger,” and the etymology of the word “anger” itself (“grief, sorrow,” cognate with words in other languages for “regret”) doesn’t really help. I have my guesses, but who knows?

    Conclusion - It seems to be chiefly British, largely but not exclusively used in a military context, and it’s not so ubiquitous as to be represented in most dictionaries. Definitely exists as a phrase though, and perhaps in some circles, it’s very common. TIL.