But what this illustrates to me is that researchers are just really careless, despite everything we make them agree to in data transfer agreements. It seems absurd to have little cubicles like this https://safepodnetwork.ac.uk/ (think Mission Impossible 1) but I do despair.

https://www.legislation.gov.uk/ukpga/1981/61/contents

https://javaalmanac.io/jdk/1.2/api/java/util/Date.html

(I can't find the 1.1 docs, but they were the same)

It's one of my favourite examples of how languages pretty much always get date and time hopelessly wrong initially. Java now has one of the best temporal APIs.

Thank you for saying this. It immediately drove me crazy.

It is reasonable to say: well if they aren't providing anything of value then the market ought to bypass them. The reality is that the publishers have been very canny in protecting their position, and sharp practice is rife.

Just to be clear this is specifically _gold open access_. There are other options like green (author can make article available elsewhere for free) and diamond (gold with no charge).

I was going to object, but probably right to just skip the horror of the true Spectrum keyboard.

You can hear Richard Brooks summarise the situation (in 2023) here: https://www.private-eye.co.uk/podcast/76

When your kernel stopped support over a decade ago (iirc) it does seem inevitable that distros will slowly evaporate.

> Most of my open source work followed Unix philosophy, so the packages did one thing at a time.

Nobody has suggested that libc -- to take the most obvious example -- is against the Unix philosophy. Debates occur around whether whether commands / daemons do too much (recent poster child being systemd) or aren't composable.

That’s an interesting difference from other Mac container systems. Also (more obvious) use Rosetta 2.