https://en.wikipedia.org/wiki/Rosetta_Stone

Maybe it's that the girls (and main characters generally) in Miyazaki's films tend to be pretty stoic, whereas Anne is incredibly talkative. Most of the show (and book as I understand it) is just her going on and on and on and on, it's her main personality trait and a source of humour.

1. https://commons.wikimedia.org/wiki/File:Torii_Kiyohiro_-_Thr...

2. https://en.wikipedia.org/wiki/Torii_Kiyohiro

3. https://www.metmuseum.org/art/collection/search?artist=Torii...

4. https://www.artic.edu/collection?artist_ids=Torii%20Kiyohiro

> the user-facing software of Facebook is categorically, fundamentally coercive. It's like an arbitrary code execution exploit running on our brains. Scrolling down is the program counter, and the content that pops up is the instructions.

https://andrewkelley.me/post/dont-take-black-pill.html#:~:te...

https://en.wikipedia.org/wiki/Trapline#Registered_traplines

https://www.nytimes.com/video/insider/100000004687429/farewe...

Isn't the borrow checker supposed to prevent these things? I was still holding an immutable reference.

https://www.youtube.com/watch?v=Hup0lsrY07I

I've also been watching the 1979 anime adaptation of Anne of Green Gables. Hayao Miyazaki worked on it (7 years before founding Ghibli), and although the TV animation is more limited than a film's, I think it looks awesome. It's pretty funny too. Miyazaki's reasons for quitting halfway through production are really interesting to read in the Wikipedia article:

https://en.wikipedia.org/wiki/Anne_of_Green_Gables_(1979_TV_...

I looked into it because I've always wanted to read Anne of Green Gables, and I had heard that PEI is a big tourist destination for older Japanese women who grew up watching the series. It's one of the few I don't mind dubbed, since it's an adaptation of an English-language work and the acting fits really well. It's probably not supposed to be on Youtube, but the entire series is:

https://www.youtube.com/watch?v=_2CmEYEeDSU&list=PLV4Ztn9euy...

https://pagedout.institute/?page=cfp.php

https://en.wikipedia.org/wiki/Subpixel_rendering

Maybe hardware- and access-aware more generally.

One of Mike Acton's other talks has a "Is Data-Oriented Design even a thing?" section, which goes over what he means when he refers to DOD:

https://www.youtube.com/watch?v=rX0ItVEVjHc&t=741s

– Gently suggests inlining

#[inline] - Really suggests inlining

#[inline(always)] – Really Really suggests inlining (still not guaranteed!)

https://nnethercote.github.io/perf-book/inlining.html

> All of the objects declared in a given scope are associated with a storage region, essentially a local heap. As an object grows, all new storage for it is allocated out of this region. As an object shrinks, the old storage can be immediately released back to this region. When a scope is exited, the entire region is reclaimed. There is no need for asynchronous garbage collection, as garbage never accumulates. Objects may grow in a highly irregular fashion without losing their locality of reference.

> Note that pointers are still used behind the scenes in the ParaSail implementation, but eliminating them from the surface syntax and semantics eliminates the complexity associated with pointers.

This approach seems to come up in many contexts, where a pointer-based address (raw pointer, reference, slice, etc.) is abstracted into a higher-level address key, usually an index integer (essentially a higher-level virtual pointer). The implementation might reallocate under the surface, or manage chunks of data through some sort of paging where the underlying pointers don't change (I was musing about this here [2]).

I guess I'm thinking out loud here, but most dynamic languages (eg. Python) don't expose the pointers or care about invalidation of the addresses, they just happily reallocate. I've barely written parallelized code, is pointer aliasing really one of the biggest roadblocks? It seems like it can be abstracted away fairly easily, even in a pointer-exposing language.

1. https://www.adacore.com/uploads/papers/parasail-pointer-free...

2. https://news.ycombinator.com/item?id=49013285

The big problem with databases, in my opinion, is the horrible API friction between them and your code (not even SQL per se). It makes sense if you're calling out to a database server and transferring data, but for the small, intermediate values we see in code every day, the relational model is amazing and yet so painful to use within a given programming language.

I've been envying the C# people and their LINQ, and the Java people and their jOOQ, because I'm either making a half-assed database in my own code with structs, arrays, and hashmaps, or I'm constructing some SQL monstrosity, shoveling it out to SQLite or DuckDB through a library, and marshalling the types back and forth.

Why can't I just have everything I want all the time?

1. https://news.ycombinator.com/item?id=49016824

2. https://duckdb.org/2022/10/28/lightweight-compression

https://doc.rust-lang.org/std/?search=with_capacity