3 ms·
Lots of people learn the same lesson at some price. Data and execution are two separate things and should remain as separate as possible. The reason is that o
by CyberDildonics 2y ago
Lots of people learn the same lesson at some price.
Data and execution are two separate things and should remain as separate as possible.
The reason is that once you mix data and execution, suddenly you don't know what your data is until you execute it. Then you can only deal with it in the context of whatever tools you write and you can never just look at it straight.
On the other hand now execution depends on lots of data and is no longer modular or general/generic and so becomes a one off solution somewhere.
At some point everyone has the "what if" idea and hopefully it only burns them instead of lots of other people through poor design.
- renox 2y agoNice theory, how do you do in the real world where you have a 'data' whose value depends on the OS used?
- CyberDildonics 2y agoWhat are you talking about exactly? This thread is about static data files. Did you think I was saying a program shouldn't have variables?