You're right that a lot of material really does require a physical book. Anything even remotely technical.
That said, I would argue that a voice actor is far more significant than page formatting when it comes to novels. A good voice actor can turn a good story great, and sometimes a poor story to... acceptable.
I've read thousands of novels over the decades, both with and without audio, so I'm reasonably confident about the above.
Embedded developers often suffer under archaic toolchains. There's plenty of reasons for that, but one of them is UB: a newer version of the compiler can completely change an embedded program's behaviour.
While true (beyond 30-50km/h), that assumes that cars are driving at a steady state. Obviously, cities with much more stop-and-go require more revving of engines.
Acoustic tyres are also gradually becoming the norm, primarily with EVs. This cuts noise by several decibels.
> There's essentially no reason to prefer the aligned load/store commands over the unaligned ones - if the actual pointer is unaligned it will function correctly at half the throughput
Getting a fault instead of half the performance is actually a really good reason to prefer aligned load/store. To be fair, you're talking about a compiler here, but I never understood why people use the unaligned intrinsics...
You can get substantial performance improvements by using guards though. See what Wings3D does with is_float() everywhere in hot numeric-heavy code.