Youre more confident that it doesn't still happen than I am though.

Unfortunately this isn't unusual, well except it actually being accepted that he was innocent after the fact.

Assembly is add R1 R2. Forth takes the 2 numbers from the TOS and puts it in those registers. That wasn't obvious what was happening in the post, I wonder if student me would have wondered.

You could make the case for going all the way down to the silicon.

We teach English, maths, science to give a rounded understanding, not to make student productive or give them information that will be immediately useful. IT/computing in secondary school should be doing a similar thing. It should remove the mystery of what a computer is. That it is programmable. Hopefully it's improved since I was young and we were basically shown how to use Excel.

It's got some extremely simple rules. 1 data structure. And nothing is particularly hidden.

Python might be better for actually producing something, but from a 'teaching how computers work' pov, forth would seem to have it's merits. Python hides a lot of stuff, thus we have a situation where people think compilers and interpreters are magical things. If you don't care how the computer works, that's fine, but personally I'd like to teach my kid how a computer works, not how to use some programming language.

Further I put a jumper on in the winter, have insulation in my house, have curtains etc to keep heat in. What's wrong with having passive ways of keeping warm or cool?

The only situation where you would have a point is micro wind generation, and that's basically no longer a thing because it doesn't work.

I'm not necessarily talking about the Unix concept of a group. It seems to me you want some granularity between 'kill all processes' and 'keep all processes'

It seems to me if you want persistence between logouts, the processes should belong to a different group/user.

(I'm spitballing hypotheticalshere, not saying anyone/thing in particular is wrong)

I don't know if it's to try and circumvent Ukrainian defenses or to provoke a reaction to sell to domestic audiences though.

And that being the case can systemd not just only close everything when your logins reach 0?

If python had you write e1.__add__(e2) Or S1.__join__(s2)

Then you would have 2 distinct operators, therefore no overloading.

Re classes.

Foo.len() and bar.len() are different. You can tell that when you are using them.

It's no different to I_add() and f_add() they are both different functions.

If you automatically called one of those depending on whether the arguments were floats or ints, that would be overloading.

I suppose you could take it further and say that it's overloading if you have different int sizes.

But then we don't really class that as overloading, which I suppose demonstrates that it isn't a very precise term so there isn't much point getting particularly pedantic about it.

Lawyers are going to use ai, because it's easy. The only time they won't is when the AI won't come up with a plausible enough excuse. The lawyer will always have a job, because a non lawyer using the same arguments will be ignored.

So these are rules to maintain the appearance that the system has integrity.

And that's the annoying thing. They know what integrity and justice and fairness look like, just as the rest of the justice system does, but they ignore it all.

At this point, it would be preferable for both sides to put their argument to an AI and let the AI decide what is fair. Wouldn't be any worse than judges who were themselves lawyers looking after their own.

Sorry for the rant, I've had experience of the 'justice' system.

This is a limitation of the rust model. You could have a language where intrusive linked lists are provably safe.

That's not to say rust doesn't work, but it's the first language I'm aware of that's attempted compile time memory safety, and no body seems to be talking about how to do it better.

Learn some facts before spouting bs.