I rather hope it doesn't. It's not so much about action; it's subtle worldbuilding and a certain vibe that is easily distorted on screen. Also, it would destroy everybody's personal vision of the Shrike...

I find it awesome that the true nature and mission of the Shrike remains a secret.

He predicted social media as well. So many themes in this work only mentioned in passing, too many to develop in full...

It starts very slowly and the worldbuilding is exquisite and you will likely uncover many facets only upon rereading it. However, it is well worth persisting.

Works with considerably more action are Olympus and Ilium.

It's ok, at best. I can tell you really like it, so for other people that should be a great indicator!

It's up to anybody to not have a particular taste for religious topics, however, spirituality (or the lack thereof) is an important part of human culture and psychology. Therefore a science fiction novel in a sufficiently different setting from Earth's early 21st century really ought to cover these topics as well, lest the worldbuilding would be very shallow and the resulting work would likely lack depth.

The point is that they seem to worry more about being a weed user than being an alcoholic.

It is a federal crime to use cannabis. They've always been concerned about it.

That's the weird thing though. One is criminalized, the other isn't. The impact on job performance is unrelated to that though.

They're assessing truthfulness. You can be cleared with a history of moderate usage as long as you disclose it. They also flag alcoholics as a risk.

Why wouldn't they? There are Discord servers about anything you can imagine and also what you can't or don't want to image. As long as they don't start disrupting their infra Discord couldn't care less.

Also, how would you even go about classifying them as botnet operators?

The Win32 ABI is also just a wrapper on the native API, which is only stable in practice, but not officially according to any Microsoft documentation.

Glibc is userspace seen from the perspective of the Linux kernel.

It doesn't really matter if it's 'just a wrapper', because said wrapper provides an ABI. Even if the underlying Native API changes, the interface the wrapper presents to other compiled binaries won't. The latter will contain caller/callee register setup, type layouts, function arguments and more for that wrapper.

Cygwin is also 'just a wrapper' for the Native API and Win32, and look how drastically it changes the ABI of applications.

Indeed, OpenBSD recently added hardening measures and started restricting the generic syscall interface to libc.

With the crucial difference that Linux places high value on syscall interface binary compatibility, while the NT native API is not guaranteed to be stable in any way.

A bit more comparable is OpenBSD where applications are very much expected to only use libc wrappers, which threw a wrench into the works for the Go runtime.