Great talk!

1:22:34 I was unsure if the double cast was needed, but now I know.

ranges/view were one of the main things why i tried making our codebase ready for C++20. Even just the small things like splitting strings. And then we saw that while you could split strings there was no way of concatenating them back together in a similar style - ok, so we have to create our own compatible functionalities for that (the committee "forgot" about that and it was later added to C++23). Still not too bad - so lets test it... wait, why is everything broken? oooohhhh views are caching... and the code would need extensive reworking due to changes to enum, bool, volatile etc.... Yup, and back to C++17.

22:38 - "Do you think cheap is expensive?" - i sure hope nobody does.

Every time he says, "It's like in C++", I say, "Oh no"; "Oh no, they will make C look like that".

Something about static rules of the system that will always be there... The emulator would always be limited in outputs for exploits, at least then. He was asked to put in signal limitations and how factors effect this but he didnt like that idea and said it would be tedious and it is already in. "get a scrub to do it..someone who can burn time.""i will have to burn through physical chips to do it and even then i would be better at working on ai or exploits."

Best programming language that human kind invented.

I don't know if I love or hate the fact that the only people using C nowadays are Python devs

1:15:00 When functions are pure, then I'd say you extend them via pre- and post-composition with other functions. And I guess with generic arguments; (as said) with functions as arguments; and maybe by application of Functors ... fns in Lists, fns in Exception blocks, fns with Logging, Optional fns, a fn in an Either, fns in Futures, ... and maybe by replacement by an Interface(?)

A brilliant talk, very well delivered, thanks Roger!

when will be a risc v laptop be a reality?

The new features are neat if they will help reduce issues without requiring modifications of the existing code. But things like that non-NULL check are wack, if you start introducing those things you might as well recompile your code in C++ with use of references if needed. Not sure why they decided to make non-NULL argument descripton so complicated. It makes literally NULL sense.

Thank you a lot!

Thank you Mike!

Compound literals, don't they also exist in Java for example?

few people get it C is infinite in scope you can do anything you want with it and in any shape you want the only limit is yourself

15:42 that int (*pk)[ sz ] [ sz ] has the *pk in parenthesis because the array operator [] has higher precedence IF the parenthesis where not to be used you will have double array full of pointers to int which is a totally and completely differnt thing from a pointer variable , more so it will invalidate the malloc call , further reasoning *pk is a pointer to int therefore Encapsulates information about the data object aka int which is a 4bytes (32bits) this encapsulation/metadata if you want to call it such is what allows the pointer arithmetic to be performed it makes the pointer aware of the data object therefore when you add/sub 1 from it it will Move the instruction pointer registers exactly 4bytes using a LEA instruction it is extremely fast

Long live C.... the grandfather of all programming languages!

Always nice to see Herb! Why is the license of cppfront still NC? This will prevent it from being included in GNU/Linux-distributions once it gets ready unless you make all contributors sign a CSA and transfer all copyright to you.

And this, kids, is why you should buy a decent mike before recording videos

I do not get it, is it a stand up ?😄

Really useful, 3x

How long did it take for you guys to fully understand the language, along with its data structures and object-oriented programming concepts??

Let me teach you an expression: "We are just drilling a hole" This expression is used in the oil and gas industry, when all the crew panic, i just reset them to calm down, it gives insurance to your teammates that you are in control. Very powerful.

This is some fantastic work, thank's James!

my rule of thumb is. If a macro changes the C syntax, you shouldn't use it

this was such a good refresher on computer architecture.

Weird people of C++ community somehow flowed into the world of C and bring this mess. Long Live C17!

Wonderful reply for the hardware and then software issue. He doesn't cooked up any story , but instead provided a brave honest reply that most of the industry is not able to solve!

I first learned C in 1984, shortly after working a long time in assembler. I could not believe that there was a high-level language that was so sloppy, did not check anything much, did not give any warnings, just let your mistakes causes crashes and even bring down the whole machine in those day. Today I love C. It's minimal, the least "high-levelness" required to get one off assembler. It's small, one can can write a C compiler in reasonable time. It's best in class for performance. Today I also love Rust. Finally a high level language that banished UB and checks almost all silly mistakes I might make. While maintaining the performance of C and avoiding the monstrous complexity and ugliness of C++. And it interoperates with C very well. So I end up loving both C and Rust for polar opposite reasons. Rust will not replace C for me, they will coexist very well. I'm sure that is true in the wider world as well.

The plugboard is just a fixed substitution. You could try to match your message allowing for constant letter replacements, and it would still match regardless of the plugboard. This is a MUCH easier problem than needing to actually OBTAIN the plain text.

The fourth rotor never turned at all. It just added an extra level of fixed obfuscation.

The Poles cracked the commercial Enigma, which didn't have a plugboard.

15:56 - wait; the ring setting not only moved the turnover notch; it also shifted the whole alphabet against the rotor wiring. So yes, that last factor of 26 should be in there.

You've reversed left and right...

Basically the perfect Internet of Garbage processor ;-)

MIPS but with extra suck factor. 68k with orthogonal instruction set and lots of internal tricks and optimizations to make it go fast, would be Genius

The problem will most modern programming languages that have a large "market share" is that they're not driven by engineering or science anymore, but by mere competition. C++ gas grown into this monster only in an attempt to keep its market share, or even grow it. (Call that user base if you prefer.) Any newer language that would introduce some new paradigms or even just some new sugar coating would become an inspiration for the next iteration of C++. Just to prevent developers from moving away. That's just plain marketing. And marketing does infect everything it touches.

can I get the presentation slide?

Hello ; I m in way to put papers : mathematics of C++. Looking for what mean classes and enumeration, as mathematical objects, (treat classes as sets definition) topology mixed with … Is there any one in this way.

Can anyone tell why the slides and godbolt output shows a call to memcpy when the actual proposal P2786 ask for a call to memmove.

I think the rules for Backstage Pass quality adjustment are the most problematic in this kata. At ~1:07:50 you mention that the refactored code has the same numbers as the requirements (10 days, 5 days) but the conditions don't match the text, i.e. " > 10" doesn't match "when there are 10 days or less" nor does "> 5" match "when there are 5 days or less" - that could be potentially confusing at first glance. You'd have to run the tests to make sure the behavior is actually correct. Also, the requirements say "at the end of the day, the values of sellIn and quality" are lowered, implying the adjustments are only done once per day. However, since rules are applied both before and after sellIn is changed when going from one day to the next, quality can actually be updated twice: right after we came into "today" and before we leave "today". These bring up some questions that relate to the correctness of the requirements and/or the implementation. I do like all the refactoring ideas discussed and demonstrated though.

The main reason to write an algorithm in a functional way: "So, here I wrote an imperative version of this [...] there's nothing particularly wrong with this code [...] but I didn't really feel very fulfilled writing this code..." ok...

Step 1. Don't write bugs.

Love this gent's style

I've been a JS/Python soydev for the past 5 years, basically because I learned to code specifically to work as a developer rather than to learn about computers. The last 6 months I've been coding multiple personal projects in C and I feel like I have a superpower now, I understand a lot of low level stuff that the high level languages hide and my code skills are much better. Probably learning C was the best decision I could make. I feel like I want to stop being a webdev because I'm sick of it, but I don't think I have the skills yet to apply for a full C/C++ job, that's gonna be a long ride.

Love this! It validates many things I tell people about refactoring and testing, things I suspect I picked up from the same sources (people & experience) as you.