Re:The "missing" graph datatype already exists. It was inven...
by WJW on Tuesday March 05, 2024 @05:00PM
(#39609658)
Probably some variation of "hardware usually influences what the optimal datatype is way more than any theoretical runtime differences". For example, B-trees for databases needing to be adapted to the block size of the underlying hardware device. Another example: As soon as you introduce any form pointer chasing to your datatype, you are often going to struggle against relatively simple array-based options because L1 cache is crazy fast compared to RAM.
Re:The "missing" graph datatype already exists. It was inven...
by benopal64 on Thursday March 14, 2024 @01:52PM
(#39706980)
Wow, great point! Thanks for the reply; I did not even think of hardware at the time of posting.
I will look into form pointer chasing. Any good reads that you would recommend for software devs who are interested in electrical engineering or rather understanding how to build hardware?
On a side note, is there a Bitter Lesson for datatypes, the way there is for algorithms?