But still yes, once NATO works out which Russian stuff to take out in response.

Probably the ghost tankers, right?

I feel like the “tits” they would get for that “tat” would be pretty bad for them. NATO breaks toys better than they ever will.

I don’t really think it would start WWIII on it’s own, though.

Ooooooohhh! I never made that connection.

What’s the problem? They’re just not sure which instance to go with?

Maybe I just like the idea of a closing tag being very specific about what it is that is being closed (?).

That’s kind of what I was getting at with the mental scoping.

My peeve with json is that… it doesn’t properly distinguish between strings that happen to be a number and “numbers"

Is that implementation-specific, or did they bake JavaScript type awfulness into the standard? Or are numbers even supported - it’s all binary at the machine level, so I could see an argument that every (tree) node value should be a string, and actual types should be left to higher levels of abstraction.

I actually don’t like the attributes in xml, I think it would be better if it was mandatory that they were also just more tagged elements inside the others, and that the “validity” of a piece of xml being a certain object would depend entirely on parsing correctly or not.

I particularly hate the idea of attributes in svg, and even more particularly the way they defined paths.

I agree. The latter isn’t even a matter of taste, they’re just implementing their own homebrew syntax inside an attribute, circumventing the actual format, WTF.

Hmm, so in tree terms, each node has two distinct types of children, only one of which can have their own children. That sounds more ambiguity-introducing than helpful to me, but that’s just a matter of taste. Can you do lists in XML as well?

I think we did a thread about XML before, but I have more questions. What exactly do you mean by “anything can be a tag”?

It seems to me that this:

<address>
    <street_address>21 2nd Street</street_address>
    <city>New York</city> 
    <state>NY</state>
    <postal_code>10021-3100</postal_code>
</address>

Is pretty much the same as this:

  "address": {
    "street_address": "21 2nd Street",
    "city": "New York",
    "state": "NY",
    "postal_code": "10021-3100"
  },

If it branches really quickly the XML style is easier to mentally scope than brackets, though, I’ll give it that.

What was the git flag to basically rewrite history again?

I’ve definitely been guilty of this, but if I can redo my changes in narrative form before I push I bet I won’t have to.

It’s a weekday, but I’m not a pro, so either llama or hamster. Maybe sloth, we’ll see where today’s project goes.

Does anybody know if there’s a standard method to do a 1-way broadcast from mobile wifi hardware? (Or Auracast, it looks like the same thing) It’s for a sort of mesh network where links may change very rapidly, and so a handshake doesn’t make sense.

Java was named after the Javanese, and not the other way around?

Why yes, future person, I’ll fix the spelling.

I didn’t get an underline because it was capitalised, apparently.

You’ll never make it as a big time web dev.

Probably not /s, sadly. It’s they that are wrong, not you.

I guess, haha. A quantum circuit is going to use something else (Josephson junction or laser), though, so even there it’s just in an auxiliary component. Except not, because this thing doesn’t sound real, at least as advertised.

Yeah, I don’t even need to read this to smell the garbage. AI + Quantum, and put together in a way that doesn’t make sense. Does it have crystals too?

Burn the heathen.

Sorry, I mean

START PROGRAM BurnTheHeathen
Burn&
the heathen !.
END PROGRAM

/s

You know, in that case, the blame doesn’t fall on the guy that made it. Shit on the people that made the development deadline a couple weeks, and then decided to keep the product in place for decades.

Yes, but they used a buzzword. /s

This is basically a clickbait critique of clickbait.

It’s a just a joke, but I feel like that actually says something pretty profound about duck typing, and how computable it actually is.

Also, it should turn an error into an empty but successful call. /s

Yep.

I’d still call that memory. It’s not the present; arguably for a (post-training) LLM the present totally consists of choosing probabilities for the next token, and there is no notion of future. That’s really just a choice of interpretation, though.

During training they definitely can learn and remember things (or at least “learn” and “remember”). Sometimes despite our best efforts, because we don’t really want them to know a real, non-celebrity person’s information. Training ends before the consumer uses the thing though, and it’s kind of like we’re running a coma patient after that.