I wasn’t aware that Java has some some catch-up and now supports user definable inline types: [Wayback/Archive] Inline Thinking | Patricia Aas – Programmer
Inline Thinking
97 Things Every Java Programmer Should Know
Patricia Aas, 16 January 2020Computers changed. They changed in many ways, but for the purpose of this text they changed in one significant way: The relative cost of reading from RAM became extremely high.…These “cache friendly” behaviors are already present in Java when using so called “primitive types”, like ints and chars. “Primitive types” are “inline types” and come with all of their advantages. So even though inline types may seem foreign in the beginning, you have worked with them before, you just might not have thought of them as objects. So when “inline classes” seem confusing, you could try to think: “What would an int do?”
Via:
- [Wayback/Archive] Patricia Aas Image may be NSFW.
Clik here to view.
Image may be NSFW.
Clik here to view. on Twitter: “Hot Take: either we need to stop teaching Big O or we need to start teaching how caches affect performance. Probably the latter, but right now people are taught mental models that don’t fit modern hardware.” - [Wayback/Archive] Patricia Aas Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view. on Twitter: “I wrote a chapter for @KevlinHenney’s book “97 things every Java programmer should know” which is also on my blog. It talks about memory access patterns and how that affects performance. Maybe it is useful for some folks.”
The rest of the thread is filled with cool messages around CPU caches and how they affect big O, so I saved it at [Wayback/Archive] Thread by @pati_gallardo on Thread Reader App.
–jeroen
