Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitates it, trying to be amusing and informative.

Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.

Is on kbin.social but created this profile on kbin.run during a week-long outage.

Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish

  • 0 Posts
  • 23 Comments
Joined 1 month ago
cake
Cake day: June 4th, 2024

help-circle


  • If we tried this in the UK with someone like, say, the late David Coleman, I’m not entirely sure anyone who remembers him would be able to distinguish - other than, as I said, the knowledge that he’s been gone for quite some time now.

    Coleman, was considered a go-to commentator for decades despite being gaffe-prone even at the best of times. He was occasionally oblivious and apparently lacking any self-awareness too. (He did kind of learn to laugh at himself though and was a good, well, sport, about it all.)

    Sounds very AI to me. Come to think of it, he may even have been kept around precisely because of the entertainment value.

    I assume that Al Michaels is not of this bizarre calibre and it wouldn’t take long for people to notice.



  • JavaScript, like some other languages of the time, was designed with the Robustness Principle in mind. Arguably the wrong end of the Robustness Principle, but still.

    That is, it was designed to accept anything that wasn’t a syntax error (if not a few other things besides) and not generate run-time errors unless absolutely necessary. The thinking was that the last thing the user of something written in JavaScript wants is for their browser to crash or lock up because something divided by zero or couldn’t find an object property.

    Also it was originally written in about five minutes by one guy who hadn’t had enough sleep. (I may have misremembered this part, but I get the feeling I’m not too far off.)


  • I’d say it’s more like setting up a handler for a callback, signal, interrupt or something along those lines.

    Function declarations by themselves don’t usually do that. Something else has to tell the system to run that function whenever the correct state occurs.

    That doesn’t account for unconditional come-froms.¸but I expect there’d have to be a label at the end of some code somewhere that would give a hint about shenanigans yet to occur. Frankly that’d be worse than a goto, but then, we knew that already.










  • Lawful good is asking for trouble. Before they know it, they’ll be inundated with e-mails to their personal company address with poorly worded help requests. They’ll spend half their time making and updating tickets on the user’s behalf that would have been mostly automatic if they’d gone the Lawful Neutral route. They need to insist requests are sent to the main support address. I’m assuming that’s tied directly to the ticketing system.

    When I was being Lawful slightly-better-than-neutral, I’d create the ticket and then put a paragraph in the reply telling them to please not e-mail me directly in future, because one day I might be unavailable and their e-mail could go unseen for hours or even days.

    Repeat offenders would eventually do it at a time when things were busy too, so I’d be concentrating on the tickets and not things to my personal address, so that slight delay often helped it sink in.