4 ms·
Found an online review of the book: https://gist.github.com/seece/25ed1b2108cf5782718b026382f2c52c https://gist.github.com/seece/25ed1b2108cf5782718b026382f2c5.
by gjadi 3y ago
Found an online review of the book: https://gist.github.com/seece/25ed1b2108cf5782718b026382f2c52c https://gist.github.com/seece/25ed1b2108cf5782718b026382f2c5...
- victor106 3y agoThanks for the link. Found this interesting and against common advice. "The bane of many projects, and the cause of their lateness, has been the insistence on not doing optimisation prematurely. The reason optimisation at late stages is so difficult is that many pieces of software are built up with instances of objects everywhere, even when not needed." There are definitely applications where performance is of primary concern (maybe only a few) and others where they are not. In apps where it is, this gives me thought that maybe premature optimization is okay? Am I reading that right? There's also this called Data-Oriented Programming https://www.manning.com/books/data-oriented-programming https://www.manning.com/books/data-oriented-programming. Are both these concepts the same?
- crabmusket 3y agoNo, DOP is basically just functional programming. There are some overlaps (e.g. separate code from data) but they're not related.