CppCon 2018: Stoyan Nikolov “OOP Is Dead, Long Live Data-oriented Design”

What people said

nikki93 · 2020-08 · Recommendation

Glad to see some agreement there. I'm interested in building an ECS-based approach for a UI system at some point. The Yoga layout engine (implements flexbox -- [LINK] ) seems to actually be pretty amenable to just incorporating as a `Layout` or `Flex` component, then you could have components for platform-specific renderings (eg. `iOSTextInput`, `AndroidTextInput`, `DOMTextInput` in wasm, ...) that could read from cross-platform common components (`TextInput`). A core aspect would also be a `Hierarchy` component that just has a parent entity id and a list of child entity ids (that it keeps in sync properly). Then bind things to JS and allow you to code it from React, while still being able to eg. run an animation thread for some specific animations that just queries and reads/writes the `Layout` and `AnimationSpec`s etc. Interesting talk re: data oriented design for a webby animation engine here actually: [VIDEO]

Read the original HN comment ↗

michael_j_ward · 2019-12 · Recommendation

Just adding a more recent video on it from CppCon 2018 where the presenter goes over a specific worked example. [VIDEO]

Read the original HN comment ↗

phaedrus · 2018-10 · Recommendation

That's a very good point. It might be question of high versus low level. From a video I watched today (the rest of the video is worth watching, too, but the following stand-alone quote is apropos): "Polymorphism and interfaces have to be kept under control. I don't believe that their role is in a very low level system like interpolating a couple of numbers in the animations, but they have their place in high level systems, in client facing APIs. They are amazing if you do a type of plug in and you really need some type of dynamic polymorphism." [VIDEO]

Read the original HN comment ↗