C Must Die
Related videos
I Watched It
ThePrimeTime
210.0k views
The PewDiePie Problem
ThePrimeTime
110.7k views
We did it?
ThePrimeTime
102.6k views
THIS BLEW MY MIND
ThePrimeTime
198.9k views
The Who Cares Era
ThePrimeTime
139.0k views
The Copilot Delusion
ThePrimeTime
245.2k views
JUST USE HTML
ThePrimeTime
327.7k views
Discord CEO Steps Down
ThePrimeTime
160.5k views
We Removed C++
ThePrimeTime
162.6k views
Devin Is A Lie?
ThePrimeTime
240.2k views
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
I Watched It
ThePrimeTime
210.0k views
The PewDiePie Problem
ThePrimeTime
110.7k views
We did it?
ThePrimeTime
102.6k views
THIS BLEW MY MIND
ThePrimeTime
198.9k views
The Who Cares Era
ThePrimeTime
139.0k views
The Copilot Delusion
ThePrimeTime
245.2k views
JUST USE HTML
ThePrimeTime
327.7k views
Discord CEO Steps Down
ThePrimeTime
160.5k views
We Removed C++
ThePrimeTime
162.6k views
Devin Is A Lie?
ThePrimeTime
240.2k views
Top Comments (10)
the CCP does not like that translated title lol 💀
Ohh, here we go again. C will die this year just like it did 10 years ago and 10 years before that.
C was always written to be machine agnostic - Dennis Ritchie famously called it a portable assembly. The issue is that C did not become more abstract but CPU's became more complex. You had more registers, different types of registers, more instructions, cache's, cores and on and on we go. The truth is assembly became abstract (virtual registers, virtual memory etc.) with most CPUs employing microcode by the 1980s. The machines became more abstract as layers of hardware were added to the machines. The increasing hardware stack complexity means there is less direct mapping between lower level programming (both C and assembly) and the hardware.
C stands for "Character Building"
The think I'm most impressed with is the translation of the article
At the electronical calculators CS course I remember the prof. presenting C as a high level laguage. I was confused as I just ended a foundamentals course in python. I undesrstood very soon why as the exam was part logical gates, part assembly and part C. Writing things in C felt like cheating.
Guy in 2020: "C must die" Guy in 2080: The guy dies C in 2080: ehehe, I am still around
0:11 "xi must die" that's -30000000 social credit bro 😭
39:32 The concept that makes those two pointers not be equal is called provenance. Explained quickly it basically means that pointers are represented in the compiler not only as the literal bits of their address, but also some metadata that says where it comes from. That means that the compiler assumes that two pointers of different stack variables are *always* unequal. And the compiler makes optimizations based on that fact.
The best thing is that the "checkadd" function (despite being horribly complex and slow and nobody wants to do this crap) is actually invoking undefined behavior itself, when it applies an unary minus operator on b (if it is negative) without checking if b is INT_MIN and it would fail horribly in that case.
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
the CCP does not like that translated title lol 💀
Ohh, here we go again. C will die this year just like it did 10 years ago and 10 years before that.
C was always written to be machine agnostic - Dennis Ritchie famously called it a portable assembly. The issue is that C did not become more abstract but CPU's became more complex. You had more registers, different types of registers, more instructions, cache's, cores and on and on we go. The truth is assembly became abstract (virtual registers, virtual memory etc.) with most CPUs employing microcode by the 1980s. The machines became more abstract as layers of hardware were added to the machines. The increasing hardware stack complexity means there is less direct mapping between lower level programming (both C and assembly) and the hardware.
C stands for "Character Building"
The think I'm most impressed with is the translation of the article
At the electronical calculators CS course I remember the prof. presenting C as a high level laguage. I was confused as I just ended a foundamentals course in python. I undesrstood very soon why as the exam was part logical gates, part assembly and part C. Writing things in C felt like cheating.
Guy in 2020: "C must die" Guy in 2080: The guy dies C in 2080: ehehe, I am still around
0:11 "xi must die" that's -30000000 social credit bro 😭
39:32 The concept that makes those two pointers not be equal is called provenance. Explained quickly it basically means that pointers are represented in the compiler not only as the literal bits of their address, but also some metadata that says where it comes from. That means that the compiler assumes that two pointers of different stack variables are *always* unequal. And the compiler makes optimizations based on that fact.
The best thing is that the "checkadd" function (despite being horribly complex and slow and nobody wants to do this crap) is actually invoking undefined behavior itself, when it applies an unary minus operator on b (if it is negative) without checking if b is INT_MIN and it would fail horribly in that case.