As troublesome digital tools are in practice, the stories of "tech execs refusing digital tools for their kids" is a trope often promoted/created by kindly put fringe actors.
Yes, there are a lot of people who wants it backwards due to their own experiences.
That said, we had some vision of learning with tailored gamified learning apps, and that has come to be in a certain cases but imho it sometimes also provided a sense of "false" accomplishments as it mostly helped with rote memorization rather than principle understanding.
The apps are in summarization often a rote thing rather than something making for deep exploration, that very forward kids might've benefited from something more "free" but a majority will end up not benefiting.
And often the practical outcome of "digital learning" in Sweden instead ended up being schools trying to save money on books by splashing random PDF's about subjects into teams folders.
Trying to help my kids on subjects often ended up being scouring those teams folders and try to reverse-engineer what the important parts and dependencies of a course has been and then go through that, with a textbook you can just flip through the relevant pages of the chapters they're working on to test my kid and go through what they were having trouble with.
Now a _very_ good teacher might build up a useful corpus (but it takes time/work) and worse teachers/schools (sadly a consequence of Swedens education privatization) often create an worse outcome than with books.
To summarize, Good real textbooks thus gives a far better chance of holding a good baseline level for education, whilst digital tools potentially could do good but in practice creates a risk for a really bad baseline without _all_ parts of the education system being good.
I played a lot of Civ1, Colonization and Civ 2. First time I tried Civ 3 I lost some city due to some culture or religious influence and ragequit (I was also working my first job at that point so didn't have as much time to spare).
Played a bit of Civ 4 and 5(or 6?) but never was really as hooked on them.
It's on that list of things I would've love to do with infinite time. Especially as it actually had a hotseat multiplayer-mode that would be awesome to put in a networked context (iirc it might've been a hack enabled with a hex-editor but it was fun).
I actually wrote some stuff directly because I was young, poor and stupid.
First year in uni my windows laptop broke, had to lug around a heavy second hand underpowered ppc powerbook and wrote some application I needed that I didn't want "bloated".
Font handling, shared memory backbuffers, network api, etc.. as I wrote in another comment. It is an API to solve over the wire graphics in the late 80s/early 90s era using idioms of that time, and already by year 2000 the problems (rasterization power) didn't exist nor is it even a suitable API surface (even less so 25 years later).
Not to mention that the complexity of X11 shots through the roof once shared buffers comes into play.
X11 was ok for it's time, but fundamentally it's an really outdated design to solve 80s/90s issues over the network in the way you solved it back then.
It is INCREDIBLY outdated and forces all graphics to flow through a crappy 80s era network protocol even when there is no network. It is the recurrent laryngeal nerve of graphics technology.
Most CPU's has signed and unsigned right shift instructions (left shift is the same), so yes it works (You can test this in C by casting a signed to unsigned before shifting).
The biggest caveat is that right shifting -1 still produces -1 instead of 0, but that's usually fine for much older game fixed-point maths since -1 is close enough to 0.
It's not ideal, the api is kind of low-yet-high-level and that brings some complications.
Move backpressure handling onto the task producer and use a SharedArrayBuffer between the producer and worker, where the worker atomically updates a work-count or current work item ID in that SharedArrayBuffer that the producer can read (atomically) to determine how far along the worker has gotten.
reply