Building a Data-Oriented Future - Mike Acton

70% Mike Acton, 30% shots of developers looking super-uncomfortable.

Please don't hire these people to record the talks ever again.

Excellent intro on Data Oriented Design, dutifully sabotaged by the TEDified idiots behind the camera. Thanks for the missing slides guys. Whoever was in charge of production is shockingly incompetent.

33:00 video editor/camera operator completely misses the most impactful slide of the talk.

I enjoyed Mike Acton's talk, as always. The biggest issue was the lack of screen time for the slides. It makes it difficult to follow along.

Why is the camera zooming on strangers? Distracting cringe.

Even Mike was looking at the slides at 33:24 but you guys don't show it to us? Who the heck cut this video? literally wtf

developers: nice a cool and interesting talk to listen to with some cool slides conference producers: let me show you our awkward looking audience all the time that just wants to listen to the topic at hand and ideally not be filmed, i'm sure you will find that very entertaining

"First you need to get those clown out" .. this guy really doesn't pull his punches.

really great talk. video was cutted weirdly though. no gained information in showing the audience (rather distracting) and also in not showing the slides when it would be beneficial to do so.

I want to see a video of him comparing the before and after of unity's codebase. I wish he could do it with ue4 as well. Anyone thinking that their game running poorly is because of hardware is wrong, because it is programmed in OOP.

I feel that for the sake of brevity and simplicity, it would have been better for Mike to show an Object Oriented Programming example that fails with rendering a large number of items on screen, then show a Data Oriented Design example that solves the problem. Then ask, "Why is this a problem in OOP, but not in DOD? Here's why..." In a mere 30 seconds, people would have been able to fully grasp the problem, understand the impact of DOD, and be primed for a more detailed explanation for the remainder of the talk. He could have very simply linked "bad OOP" to "cell phone battery dead" instead of explaining it like a drab college lecture on logic.

See Mike Acton with the talk — instant like

Camera was distracting. We came to watch actual data not storytelling of the conference. Such irony is beyond my capacity to handle!

thank you camera man for pointing at literally every women in the crowd. Like "ah yes, it's not all men here, see look: these two"

33:00 nice that the regisseur decided to film the speaker and the audience instead of the most important thing...

This is a tech talk not a Hollywood reception. Please record the slides and the speaker. No one cares about the attendees.

Gotta say, most videos on YouTube I view in 1.5 - 2 speed but Mike… Mike I need .75 to make sure I absorb it. He’s real close to my college C teacher back when I hated coding but liked engineering.

I've snubbed Unity for using C#, but this really convinces me. Low-level rendering code in C++, Shader Languages, and GPU Rendering APIs, with HP C# being used for ultra-performant scripting. Very different than the XNA C# of old. I've been on a Rust, Zig, Jai kick for a while now, but I've always had a partial fondness for C# (when comparing to Java) and the fact that it's this well-opinionated subset is actually incredibly appealing. I wish I was more clued in about this earlier.

I am a Linux user (current Unity version is real crap there). This talk almost got me installing Windows to try these Unity features