Pitfalls of Object Oriented Programming, Revisited - Tony Albrecht (TGC 2017)

[connorclark]

Wish the camera would just stay focused on slides. Stop showing the audience

[TheMrTka]

ADHD Operator moments:
19:00 first adhd attack started
19:52 first adhd attack ended
20:10 second coming
21:05 Thought about showing himself to the camera
21:25 "Nah, changed my mind"
22:15 "What's there on the left?"
22:32 "heh, shiny baldness"
23:12 "Oh, right, I'm the operator here"

26:35 "Wow, are those League of Legend bytes?"
27:26 "And what a stack do I see here?"
27:31 "Damn it, so slow camera"

36:40 *starts shaking intensively*
36:50 "Time to fly"
37:36 "All right, time to return"

46:24 "Phew, my job is done"
48:09 "Now who's talking here?"
48:17 "Nevermind"

[lepidoptera]

This went over the heads of 99% of young developers who had never thought about runtime machine level issues before.

[psybertao]

Genius. "The language is not your platform."

[danieleccleston]

This seems good, I'm trying find more content like this but it's a bit hard

[styleisaweapon]

~36:40 not better branch prediction, just much deeper speculative execution than before (if it happened at all with indirect function calls back then)

[uvata]

Devirtualization should still yield a gain, but he loses cache coherence here -what should have been done is to inherit both Object and Node from something that has a boolean if it is object or node (or an enum, if you have more), then where you originally do virtual functions, just do a regular "if" statement on this field (or case for enums).

Should be faster IMHO.

PS.: Just having an extra field that both class inherits does not make it need a vtable and you can just cast the "whatever" into that type so it really is just an if statement...