AnyOldName3

I’m thoroughly an adult (somehow?) but when I was at school, they mostly taught us the absolute basics over and over and anyone who hadn’t picked something up when they were five probably wouldn’t by the time they left school. It probably doesn’t help that the kind of people interested enough in computers to learn to use them properly and well enough to explain to children could also get a much more lucrative job doing something with computers than teaching children.

In the UK, it’s because it’s the defence’s job to notice this kind of thing, but paying for a good lawyer is life-ruiningly expensive, and public defenders via legal aid are paid hourly, but have a cap on the number of hours that’s never enough to deal with anything properly, so are either rushing everything and miss things, or are massively overworked and earning well below minimum wage when their unpaid work is included.

I don’t know if the same problems extend to Canada, but it’s fairly likely, as the adversarial approach just inherently means the defence has to do loads of things that would be someone else’s job or not need doing at all under alternative systems, so you have to have a trained professional doing lots of work, and that’s inherently expensive, but taxpayers don’t like spending money on defending people who probably did crimes.

It’s not as good as the solution for alcohol as one bottle of beer making it to a child gets used up after only giving one child one drink. Once a token leaks, it can be shared again and again and used by arbitrarily many children arbitrarily many times until someone notices that it’s leaked and revokes it (which then means that websites need to actively update a list of revoked tokens instead of just relying on public key cryptography to confirm it was signed by one of a few authorities, or all tokens will need to expire automatically after a short time).

It’s not really the intended use case of Lua to be used in things that will be upgraded after they’re released. It’s meant for things that need to work exactly the same way in a decade as they do now, and that’s best served by sticking to a specific version and either only upgrading to bugfix releases, or sticking to one specific commit forever. Those use cases also are better served by sticking to old versions of any libraries they use that are written in Lua (otherwise they might be hit by regressions or turn out to have been reliant on old buggy behaviour that’s been fixed), so probably aren’t upgrading to newer versions. That’s why the article is making the point that it’s not worthwhile for the maintainers of those libraries to keep compatibility with old versions of Lua as the people still using old versions of Lua are probably going to be sticking to old versions of those libraries, too.

I’ve not seen it so much with Java, but for Lua, it’s not an English word, and most things in software are either English words or acronyms/initialisms, so it’s usually a safe heuristic to assume anything that isn’t an English word should be capitalised.

It’s Lua, not LUA. It’s Portuguese for moon, not an initialism.

You can’t migrate once you’ve got a plugin ecosystem because you’re not the maintainer of all third-party plugins, and the maintainers might have lost interest or died and used a licence that doesn’t let anyone else take over.

There doesn’t really need to be as they’ve stuck to the same series for decades now.

Technically it was the Free Software movement that was a form of Leftism, and Open Source was Capitalism’s attempt to subsume it once it became apparent that it was capable of producing better software.