3 ms·
> Except in a database, the data in most programs is a minor player. I guess that depends on what your definition of "most" is. A large portion of C code eithe
by humanrebar 13y ago
> Except in a database, the data in most programs is a minor player.
I guess that depends on what your definition of "most" is. A large portion of C code either depends on hardware interfaces or is intended to be optimized. In both cases, the layout of your memory (data) is extremely important to an implementation.
One of the biggest criticisms of OOP is that it tends to obscure data layout, which isn't always an implementation detail. Interestingly, the patterns described here are subject to the same criticisms.
- brandonbloom 13y agoAlso from that same paragraph: > The design and implementation of algorithms constitutes the vast bulk and difficulty in developing software. That's just a crazy statement to me. In my experience, the bulk of developing software is anything but the design and implementation of algorithms. And I've worked on some pretty algorithm-heavy projects! I don't even know where to start rebuking the rest of this article's discussion of data and I suspect that the author and I simply have dramatically different definitions of the word. Regarding your comment: > One of the biggest criticisms of OOP is that it tends to obscure data layout, which isn't always an implementation detail. I'd argue that OOP obscures data representations more broadly than just data layout. Encapsulation is great, but it's simply the wrong default: Representations and the scope of their exposure should be carefully considered. Further, immutability greatly reduces the value of encapsulation.