Відео

thank you for such a beautiful language

the essence of c++ = cringe

both bjarne stroustrup and herb sutter are my idols for a decade now, whenever i listen to them talk, im just amazed and glad as if im watching a movie

that slide about removing c preprocessor --- the best one, and then the one who shows modules and other new stuff as an argument... ftw

Thanks!

Thank you !

The next programming language is C++26.

C++ for the 2030's!!!! 2030 times more unreadable hahaha

Such a great presentation, Zain. Highly relevant even today as people aren't really fully aware of product manager's responsibilities.

Really good talk, even if it isn't what I was looking for.

This guy is a living legend !!! I grew up with C, as no commercial C++ compilers were available... and when they popped up, most were actually pre-compilers, generating (barely readable) C code. I'm actually pleased to see Bjarne emphasising the 'essence' of C++... I've seen so many nerds 'looking down' to older C/C++ guys & girls, because they were not aware of the latest C++17/20/23 updates... which are definitely NOT the essence of it !!! A good C++ dev should also be a master in C, and even have some serious notions of CPU architecture and assembly language... just some Gen X's opinion ;-)

Thanks for your video. C++ makes me feel good.

absolute legend

Start 1:19

I think it's a failure blaming Powerpoint for this (likely coming from prejudice against it). It would have been incredibly easy to use some big red bold underlined font for the data showing risk, it would have been easy to give the dlide a big, red title with the words: WARNING, HIGH RISK OF FAILURE and so on. The same people would have done the same using other presentation software, It doesn't matter what tool you use if you are wildly unclear about your main statement. The message many people gets from this is: Powerpoint killed those people. No, it wasn't Powerpoint. It wasn't even the slide or too many numbers, or badly formatted indents. It was those Boeing engineers, who didn't have the courage to warn NASA that they have no idea what's going to happen but it looks dangerous.

There's something about Nokia and C++ in the same video lol

That zero cost abstraction is a BS. Never true.

And thanks!

Thanks!

I wish that section about mocks was a little UA-cam video on it's own, so I could use it to troll crappy tests. :)

This is all that is wrong with "modern" C++. There's a great way to handle errors in C++, it's called exceptions and all the other things should have never made it into the standard library!

glad to see bjarne in the end of this years

It is absolutely insane to be head in the sand about Rust at this point

I've actually seen a piece of code where there's one copy of the data in a (sort-of) ORM derived object with some of the required fields and then a raw SQL derived hash with some of the other required fields. This is a use-case for 34:40 naming one of these userOBJECT and the other userARRAY ... ... ... although... "there are other solutions to this problem" ;)

Do they really need to imagine who Bjarne Stroustrup is?xD

He should be playing Rick by now.

Awesome! Great tricks!

The reflection thing is going to be revolutionary. Right now, I am using boost::pfr to iterate through struct members, and it is awesome.

27:00 how does this work? Shouldn't you need the null terminator?

What is more intuitive and declarative this: // select all member function of // struct options auto mem_funs = select * as foo from Options where std::is_mem_function_v<foo> and std::is_public<foo> and not std::is_static<foo>; Or what was presented in the video?

c++ is a hoarder’s apartment.

Just use a simple keyword for gods sake. Unfortunately c++ is becoming an emoji language. What is next?

I'm excited to see C++ become so powerful and intuitive. I learned C++98 during my undergrad (2016-2020) which was great, but since embracing modern C++, it's been an absolute blast

6:50:56 Mathieu’s talk from 2023: ua-cam.com/video/NTZ_zUp8uyA/v-deo.html

6:14:42 I believe the “my_caller” handle is typically called “the continuation” of the Async task

5:57:03 Andrzej’s talk from 2023: ua-cam.com/video/ZSkign_3Hp4/v-deo.html

5:50:07 Andreas’ talk from 2022: ua-cam.com/video/NV429-sI5Ew/v-deo.html

22:55 Introduction and Discussion Panel 35:49 Andrezj Krzemieński - The C++ Way 1:34:52 Wenjin Yu - Unlocking Performance in C++: From Profiling to Optimization 2:52:57 Bartosz Moczulski - Shadow Stack, fix memory corruptions immune to stack-protector 3:50:23 Filipe Mulonde - Implementing Large Language Model (LLMs) Inference in Pure C++ 4:58:42 ⚡️Dawid Dulian - How to enjoy the templates - Introduction to concepts (C++20) 5:23:00 ⚡️ Michał Prorok - Design Thinking - not only for extraverts! 5:49:34 Andreas Weis - Deciphering C++ Coroutines - Mastering Asynchronous Control Flow (part 2) 6:49:00 Mathieu Ropert - Heaps Don’t Lie - Guidelines for Memory Allocation in C++ 8:04:42 Damian Gwiżdż - Optimizing C++ Compilation: From Unity Builds to Low-Cost Data Access (LCDA) 9:04:01 Radosław Szewczyk - Building NLP classifiers from ground up: C++ and Python binding

Please clear this fact are there 44 keywords in C23 ?

2:55:48 Khalil Estells talk from ACCU 2024: ua-cam.com/video/BGmzMuSDt-Y/v-deo.html

memory safety... do it. skip the next conference and add memory safety

1:49:52 The graph supposedly shows that the "normal" O(n) algorithm stays close to "fast" which is O(log n). This is not how log n looks in log-log scale.I think there is a mistake there.

A czy slajdy z linkami będą dostępne?

00:00 - introduction 03:32 - outline of the talk 03:55 - modern hardware; memory access and cache 11:20 - how reading from cache works 13:50 - cache implications 14:40 - Data Oriented Design 17:02 - AoS vs SoA 26:09 - data oriented transforms 27:08 - code coupling 27:54 - data coupling; threads 33:50 - entity control system 45:00 - summary 46:01 - Q&A

How to handle the case that an Actor process is killed (as is common in k8s)? Are the entries in the actor's message queue then lost, or are they persisted and resent to another actor? Could we achieve idempotent behavior when sending the same message (with an unique message id) to the same actor twice or to different actors in parallel? What about time-out constrains for messages?

I dropped out of CS at uni and I don't know how to make my own programming language :(

5 principles: 1) 1 idea per slide 2) SIZE matters 3) Six lines (body) 4) Value = solution/data that audience finds valuable 5) Contrast

3.10

"Clearly you can't do this". Ah. yes. I erm um, no I can't see it

A very good presentation here.