> I wonder how much of the push towards LP64 (ints are 32 bits, pointers and longs are 64) was to match Java. It was to avoid breakage when porting existing pr

> I wonder how much of the push towards LP64 (ints are 32 bits, pointers and longs are 64) was to match Java. It was to avoid breakage when porting existing programs. > I think this is one place where Swift (among other modern languages) has it right. We used to do ILP64 in Rust and we got a huge number of complaints; there was work by a significant segment of the community to fork the language over it. The memory usage argument is still very important to a lot of people.