The impact of manufacturing costs and price sensitivity on book sizes:
https://www.antipope.org/charlie/blog-static/2010/03/cmap-5-why-books-are-the-lengt.html
Many of these constraints disappear for ebooks!
Related Posts
On thinking of books like software, treating them as evolving artifacts, and URLs versus paper book publishers: https://cs.brown.edu/~sk/Memos/Books-as-Software/
It took me way too long to realise that Arc<Mutex<T>> is basically a way to create multiple &mut T references (with runtime constraints).
This means that you can use plain &T and &mut T in the vast majority of your code. Most code doesn't need to care there's a mutex.
Trying to let my 3yo try as many different technology interfaces as possible.
Mouse: not too bad, especially after reducing sensitivity.
Keyboard: WASD is easy to lose track of in a sea of buttons.
Controller: requires both hands together, which is tricky. Arguably the left hand is more important too, hard for a right hander.