Very good examples of DoD, will have to take his advice and look into chromium. Unfortunately DoD now feels like the hammer in my hand, and all my projects are nails! Will have to exercise some restraint :)
It tends to be closer to procedural or functional with the emphasis on transforming data. Typically that immediately demolishes much of the structure and hiding of data that OO tends to emphasize with encapsulation.
I look at DoD as writing code with a pattern similar to what finally runs on the CPU. When you do that, it's much easier to reason about how it will run on actual hardware. Other coding paradigms that don't at all resemble the procedural nature of CPU execution rely quite a bit on the promises and capabilities of the language/compiler to deliver "zero-cost abstractions". Because, in the end, whatever you write gets translated to procedural machine code.
40:41 - tree hierarchy of css
42:00 - algorithm has to know hierarchy
Very good examples of DoD, will have to take his advice and look into chromium. Unfortunately DoD now feels like the hammer in my hand, and all my projects are nails! Will have to exercise some restraint :)
Insanely goood talk!! Motivates me to tinker with it!
Looks like procedural programming.
It tends to be closer to procedural or functional with the emphasis on transforming data. Typically that immediately demolishes much of the structure and hiding of data that OO tends to emphasize with encapsulation.
I look at DoD as writing code with a pattern similar to what finally runs on the CPU. When you do that, it's much easier to reason about how it will run on actual hardware.
Other coding paradigms that don't at all resemble the procedural nature of CPU execution rely quite a bit on the promises and capabilities of the language/compiler to deliver "zero-cost abstractions". Because, in the end, whatever you write gets translated to procedural machine code.