Holly crap you know how hard this video is to find if you don't know the specific title. It doesn't show up on the topic search at all. They really need to put the topic in the title and keywords in for this. Which is a shame because it's a fantastic video. It would get a hell of a lot more views if that was fixed.
I keep advertising it to everybody. I even talked to Sean about it a touch (he actually didn't know about it despite working on Chromium OS). Someone from Chromium should make a talk.
What a great talk. Watching it in 2023, it provides better understanding why Swift went for Actor model to do the concurrency. Not even GCD is good enough.
Can’t we add a better scheduler to Asio that satisfies the executor model and voila, Asio is now also a tasking system. It probably isn’t that much work.
Ehh, he's passionate, you can tell that by the level of depth he gets into. He's just a very monotonous speaker so it doesn't come across charismatically.
Coding is all fun and games (yeah, right) until you start making browser based applications. Then you realize everything has to be changed to javascript and that your user will hate the interface because being in a browser, it limits all kinds of normal practical user interface behavior. Watching Sean's talks I become more and more thankful for the pains of learning Rust, because I feel like I could never hold in my head all the possibilities that could go wrong - that are baked into c++ behavior under the hood. Like you'd hope std library would take care of things in a way that the implementations don't allow something unexpected to happen between the lines of your code, but in fact you still have to be aware of the possible events every step of the code.
Holly crap you know how hard this video is to find if you don't know the specific title. It doesn't show up on the topic search at all. They really need to put the topic in the title and keywords in for this. Which is a shame because it's a fantastic video. It would get a hell of a lot more views if that was fixed.
Sean should make a talk about Chromium's task system and function binding implementation. Those are extremely well made, though lacking some features.
I keep advertising it to everybody. I even talked to Sean about it a touch (he actually didn't know about it despite working on Chromium OS). Someone from Chromium should make a talk.
@@denisyaroshevskiy5679Yes. Let's copy the multiple hundreds of megabytes monstrousity. It's awsome.
There is a problem with the semantics of try_push, you move a task into it, but you don't necessarily invalidate it!
3:30 good to see Adobe has some browser based tool 5 years ago. It is slight ironic referring to Adobe acquired Figma for $20B five years later.
What a great talk. Watching it in 2023, it provides better understanding why Swift went for Actor model to do the concurrency. Not even GCD is good enough.
Can’t we add a better scheduler to Asio that satisfies the executor model and voila, Asio is now also a tasking system. It probably isn’t that much work.
46:30 Futures
In the beginning he told that it is London subway in the photo, but it is not London subway. Downvoting this video.
This is the Khreshchatyk station in the Kiev Subway)
photos.wikimapia.org/p/00/00/34/39/61_big.jpg
Good to see you focused on only the important parts of this talk...
@@seditt5146 "That is zee joke!"
My goodness, how bored is the speaker?
Ehh, he's passionate, you can tell that by the level of depth he gets into. He's just a very monotonous speaker so it doesn't come across charismatically.
Coding is all fun and games (yeah, right) until you start making browser based applications. Then you realize everything has to be changed to javascript and that your user will hate the interface because being in a browser, it limits all kinds of normal practical user interface behavior.
Watching Sean's talks I become more and more thankful for the pains of learning Rust, because I feel like I could never hold in my head all the possibilities that could go wrong - that are baked into c++ behavior under the hood. Like you'd hope std library would take care of things in a way that the implementations don't allow something unexpected to happen between the lines of your code, but in fact you still have to be aware of the possible events every step of the code.
YOU MAY END A SENTENCE _WITHOUT_ "OKAY" FFS