3 ms·
Naming things, and cache invalidation :). Now seriously: while reading this, and especially the first problem, my head was shouting "immutable data structures!
by otikik 5y ago
Naming things, and cache invalidation :).
Now seriously: while reading this, and especially the first problem, my head was shouting "immutable data structures! immutable data structures!".
The author surely must have encountered IDSs during their 10-year tenure with Lisp. I'm curious about why they thought they would not fit the bill for the problems they are writing about.
- NyxWulf 5y agoDid you read the article? The entire discussion was on the tension between immutable data structures and cognitive complexity on one side, and machine performance and mutability on the other side.
- otikik 5y agoFirst, if I sounded snarky I apologize. I assure you it was not my intention. Secondly, I did read the article. If they are allocating a big chunk of memory and copying it over every single time they are making a change, they are not using immutable data structures. Ok, technically speaking, they might be. But they are using the worst implementation possible as a base to make conclusions from. That'd be like looking at the C language and concluding that strong types are not good, because of all the limitations C has.