They wouldn't though, even if 5% of their missiles/nukes work, millions would die.
Nighed
I didn't see Pratchett on the list, even if you have been through the Diskworld before, the re-reads often reveal things you missed.
I'm not as well read as you, so have no idea if that actually matches your taste.
Another (older though) lesser known series is the Dragonriders of Pern. Great if you like to follow a lot of characters (in their own mini series) that interact over an 80 year main series. Starts as fantasy, becomes sci-fi (With dragons!)
They are made/broken by if you like how he describes space battles though. A number of people I have suggested them to hated them, while others liked it.
There is also at least one place where he breaks the in universe rules of physics that really annoys me. (Information travelled in system faster than light)
EF can have big problems with "Cartesian explosions" if an object has two lists of sub objects to return, it will get listA length x listB length items due to how the joins work. You can see how this leads to the explosion part of the name (with more objects or lists).
Their solution is a "split query" option, that does each sub table as a separate query, then seamlessly gives you the combined result.
If a change like this let's you get those different table lists as distinct lists with the processing and round trip time of multiple requests then it could be a game changer.
(Source - my last week 🤣😭 + lots of EF docs)
SQL returns subsets of all tables with only those tuples that would be part of the traditional (single-table) query result set
So it returns only the data that would be returned from the query, so the filtering is done.
I can see some uses of it. If you look at what something like Entity Framework does behind the scenes to return nested objects, you can see how something like this might help.
Art station, Instagram and deviantart are all selling data or doing iffy AI stuff as far as I can tell.