Пікірлер
@TheTimur123 Күн бұрын
Calling async_accept_one() inside body of async_accept_one looks like requestAnimationFrame in javascript!
@testpm-il7qq 3 күн бұрын
thank you for such a beautiful language
@ViolentFury1 3 күн бұрын
the essence of c++ = cringe
@b0570nk4 5 күн бұрын
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
@b0570nk4 5 күн бұрын
that slide about removing c preprocessor --- the best one, and then the one who shows modules and other new stuff as an argument... ftw
@numv2 7 күн бұрын
Thanks!
@numv2 7 күн бұрын
Thank you !
@rickr530 7 күн бұрын
The next programming language is C++26.
@syntaxed2 9 күн бұрын
C++ for the 2030's!!!! 2030 times more unreadable hahaha
@haris_muneer 9 күн бұрын
Such a great presentation, Zain. Highly relevant even today as people aren't really fully aware of product manager's responsibilities.
@MarieAmeliaFreyaAster 13 күн бұрын
Really good talk, even if it isn't what I was looking for.
@philippeannet 15 күн бұрын
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 ;-)
@michaelhollis5749 12 күн бұрын
I could not agree more! Over modernizing the language dilutes much of its pure essence. I have a much better appreciation for the language having taken a deeper look into C, and using other languages like Go, Java, and a smidgen of Ruby and Python. C++ is best when utilizing its C background and bleeding in minor parts of the STL for ease of use when absolutely necessary.
@wmprogrammer1001 17 күн бұрын
Thanks for your video. C++ makes me feel good.
@zurrutikGames 17 күн бұрын
absolute legend
@kellyaquinastom 18 күн бұрын
Start 1:19
@mikloskallo9046 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.
@valmirius 24 күн бұрын
There's something about Nokia and C++ in the same video lol
@jur9103 28 күн бұрын
That zero cost abstraction is a BS. Never true.
@gtdcoder 26 күн бұрын
This comment is BS
@jur9103 26 күн бұрын
@@gtdcoder you pay with compile time, you pay with runtime. Debug builds are crazy slow. Where is that zero cost abstraction? Tell me. That you maybe have release builds fast? Not true in many cases. They are never able to match C performance, never mind about non readable code where even simple things looks like something from science fiction movie. C++ has been moving last 10 years in wrong direction. It is language that has helped create many jobs in cyber security field. hurray!
@gtdcoder 26 күн бұрын
@@jur9103 More BS
@Troyseph 16 күн бұрын
well clearly it soemtimes is, or noone would say it...
@jur9103 16 күн бұрын
@@Troyseph Yes, sometimes in release builds it is. We can agree on this ;)
@guilherme5094 29 күн бұрын
And thanks!
@guilherme5094 29 күн бұрын
Thanks!
@edgeeffect Ай бұрын
I wish that section about mocks was a little KZbin video on it's own, so I could use it to troll crappy tests. :)
@jvillasante Ай бұрын
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!
@plusquare 23 күн бұрын
exceptions are not great
@budiardjo6610 Ай бұрын
glad to see bjarne in the end of this years
@rjScubaSki Ай бұрын
It is absolutely insane to be head in the sand about Rust at this point
@dimi144 Ай бұрын
What does Rust have to do with this? It's just an interview with the creator of C++, I don't see how Rust fits in the picture here
@rjScubaSki Ай бұрын
@ it’s not an interview. It’s a presentation about the future of C++, and is completely oblivious to the main issue C++ needs to address to go forward. Rust and the concept of memory safety won’t go away because some C++ stick their fingers in their ears.
@heavymetalmixer91 Ай бұрын
@@rjScubaSki You forget one very important fact: Companies and industries most of the time don't choose a tool because it's the best, but because it requieres the less time to get used to, and that includes tools already in use. C++ is so rooted in the industry that at this point it's almost imposible to replace it, even how convoluted it is.
@rjScubaSki Ай бұрын
@@heavymetalmixer91 That doesn’t mean C++ ‘leaders’ should be complacent. Nothing lasts forever.
@bocckoka Ай бұрын
@@rjScubaSki many people are fine living through their entire lives that way. Anyway, C++ will never have that without dropping their legacy and becoming Rust, so there is really little to gain by talking about that. At least he doesn't bother the people whose still open to be convinced.
@edgeeffect Ай бұрын
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" ;)
@gamb5730 Ай бұрын
Do they really need to imagine who Bjarne Stroustrup is?xD
@bocckoka Ай бұрын
He should be playing Rick by now.
@pyajudeme9245 Ай бұрын
Awesome! Great tricks!
@codediveconference Ай бұрын
We’re glad you enjoyed the lecture!
@pyajudeme9245 Ай бұрын
@@codediveconference I loved every bit of it, and subscribed to the channel!
@pyajudeme9245 Ай бұрын
The reflection thing is going to be revolutionary. Right now, I am using boost::pfr to iterate through struct members, and it is awesome.
@ZaneMouakket Ай бұрын
27:00 how does this work? Shouldn't you need the null terminator?
@_shogun Ай бұрын
The stack is probably initialized to all zero by the runtime, so the print will read out the buffer but into a 0
@ZaneMouakket Ай бұрын
@_shogun Ahh. That makes sense, thank you!
@Voy2378 Ай бұрын
Depends, if prints understands it got passed size 6 array it will work. But anyway that is not the point of the example, it is about security.
@dadisuperman3472 Ай бұрын
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?
@lukasnavickas3201 Ай бұрын
c++ is a hoarder’s apartment.
@gogdarag Ай бұрын
Just use a simple keyword for gods sake. Unfortunately c++ is becoming an emoji language. What is next?
@cuda_weekly Ай бұрын
The problem with using keywords is that it turns what was an available identifier into a reserved word. Also, C++ != Pascal.
@KhalilEstell Ай бұрын
That would break code.
@IsaacKripke Ай бұрын
C++ already has nearly 100 keywords in addition to “identifiers with special meaning”. At some point a line has to be drawn.
@metaltyphoon Ай бұрын
@@IsaacKripkewait till you find out Swift have over 200 keywords
@IsaacKripke Ай бұрын
@metaltyphoon the COBOL standard has over 300 keywords, with some dialects having 2-3x more.
@jamesdowner Ай бұрын
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
@codediveconference Ай бұрын
The language is evolving, becoming even better and more accessible. It’s great that you have such comparisons and insights :)
@literallynull 23 күн бұрын
Learning C++98 in 2020 is wild
@Roibarkan Ай бұрын
6:50:56 Mathieu’s talk from 2023: kzbin.info/www/bejne/hIW9kK2LpZ2or6M
@Roibarkan Ай бұрын
6:14:42 I believe the “my_caller” handle is typically called “the continuation” of the Async task
@Roibarkan Ай бұрын
5:57:03 Andrzej’s talk from 2023: kzbin.info/www/bejne/kITOmpqklJh7ppY
@Roibarkan Ай бұрын
5:50:07 Andreas’ talk from 2022: kzbin.info/www/bejne/hIeXY2xjqK5oe9k
@Roibarkan Ай бұрын
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
@Mevilean Ай бұрын
Please clear this fact are there 44 keywords in C23 ?
@Roibarkan Ай бұрын
2:55:48 Khalil Estells talk from ACCU 2024: kzbin.info/www/bejne/eHjQq4CriKmnY7s
@AdrianMNegreanu Ай бұрын
memory safety... do it. skip the next conference and add memory safety
@AlfredoCorrea Ай бұрын
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.
@codediveconference Ай бұрын
Thank you for the observation, we will look into it.
@czeslawstoduly9760 Ай бұрын
A czy slajdy z linkami będą dostępne?
@codediveconference Ай бұрын
Cześć, niestety nie udostępniamy prezentacji naszych speakerów, ale mamy nadzieję, że mimo tego wyciągnąłeś dużo wartościowej wiedzy z naszych prelekcji. Pozdrawiamy 😊
@ДаниилИмани 2 ай бұрын
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
@nikolabanovic4833 Ай бұрын
bless you
@micknamens8659 3 ай бұрын
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?
@jazzochannel 3 ай бұрын
I dropped out of CS at uni and I don't know how to make my own programming language :(
@dawiddulian2403 3 ай бұрын
5 principles: 1) 1 idea per slide 2) SIZE matters 3) Six lines (body) 4) Value = solution/data that audience finds valuable 5) Contrast
@AhmadAli-kv2ho 3 ай бұрын
3.10
@linkVIII 3 ай бұрын
"Clearly you can't do this". Ah. yes. I erm um, no I can't see it