I can't even imagine a hacker that discovered this

Fascinating

Guys what ever programming language you're using doesn't matter (c is very safe and hackers aren't that genius to find memory leak) social engineering is the problem. I am web developer i see how easy it is to hijack JWT and use it to bypass authentication and it has nothing to do with c.

This needs to be automatically understood without explanation

You shouldn't have come back. React is pure garbage, yet everybody seems to love it.

Unfortunately most league players won't care unless it'll start breaking their computers or the game itself. Well, maybe Vanguard will at least get me to stop playing league

I'm in the exact same boat, my friends and i all stopped playing League since this vanguard, it's sad we were having so much fun together... I'm thinking about buying a new computer just for this but the hassle of having 2 computers at one desk is just not worth it for me atm...

"I wont talk about this very complex algortihm." Procced to talk about this very complex algorithm

Does this guy always has to have the words "HEAP" and "C" on his videos? 😅

This is absolutely the greatest video on how to not use a smart pointer. To illustrate it better, here is an equivalent code of the first example in Rust. struct Dog { pub name: String } impl Dog { pub fn speak(&self) { println!("bork bork i am {}", self.name) } } // taking ownership of dog just to release the ownership aftwerwards??? fn do_something_with_the_dog(dog: Box<Dog>) -> Box<Dog> { dog.speak(); dog } // just borrowing it, nice fn do_something_with_the_dog_corrected(dog: &Dog) { dog.speak(); } fn main() { let mut ralf = Box::new(Dog{ name: "hihihi".to_string() }); ralf = do_something_with_the_dog(ralf); // blasphemy! do_something_with_the_dog_corrected(&ralf) // ok, should have used this instead } See how egregious the first function is? If you need a borrow/view to a value, even if it's in the heap you can just take a reference/pointer to it (std::unique_ptr has a dereference operator, use it to get a reference to its value). His "solution" to this problem is barely a solution. Using shared ownership as the first solution to lifetime issue is rarely do any good, it should be the last ditch effort. Instead, try to restructure your code better so that the ownership and lifetime of objects are clearly defined.

We used to do this back in the day. I cant even remember what it was called at the time but I would use this method to keylogg p3ds. Those yahoo chat days were crazy

If US says it is safe is because it has a backdoor

i have a really good question... how do you feel about adds? how about some web pages running crypto coin miners through legal means.

This is so relatable. Looking back on moments like these really help us see how far we have come in our learning journey.

He's simultaneously pranking / punishing the type of person that would actually believe that you can learn assembly in such a short amount of time by teaching using AT&T syntax! "I know - let's choose the syntax that was the brain-child of a freaking telecom company instead of the one from an actual chip designing / manufacturing company - Intel!" - said no one EVER!!!

explooet

I love this but don't understand yet

Great info! Thanks 🍷

Great, now you want me to learn C???

really ? again ? an other backdoor on cisco ?... man it's been 20years and this shit doesnt change

So, why do you let a user to access over array_size and don't check it? Ofc it takes some CPU ticks to do if() check, but other langs do this check implicitly. In C you can do it without checks if you sured that you are accessing right memory and it will be faster then in others langs. You can balance safety and performance as you need for your aims.

It was so unclear back then how publishing and even connecting worked.

Millions of toothbrushes used in cyber attack! (HOLY COW, WHAT ABOUT MY TEETH :O)

0:03 LMAO my bluetooth driver croaked at the perfect moment that was beautiful.

The beginning of every coding book should be dedicated to buffer overflows.

Dude fix your stereo channels.

Accurate.

It's portable assembler; of course it is dangerous.

Now THAT is an interesting use of a huffman coding tree.

This is why i let my highschool teach me problem solving, now i have a really good problem solving base and even some optimisation skills (i always try to make everything as fast as i can)

Lol

You can use composite functionality to achieve the exact same thing as here without gotos, however, where gotos shine, is making specific jumps out from multilevel iterators (like nested loops) that can get very messy and have to do extra steps without them edit: meh, only now noticed this was and old video and others had already commented the same thing

Tell that to the morons on middle management 😂😂😂😂

Okay that’s cool and all but why are you using vim💀

it rhymes with gonad

Awwwwww😊 Imagine doing it for a living… but in React 😂 That’s my life rn

Games lik this shud be ban from net and shut down they spy stealing Real life infos this arent legal same as face book spynon all and sell your date

Now you know how Art Majors feel 😂

use cpp stupid

I am actually interested at how do you check what you do on C, in the assembly editor.??? intrigued actually :)🤔🤭

Style guides are important for being able to review code in the form of diffs without dealing with unnecessary irrelevant changes. The google guidelines aren't even the best. But actually having the best style guide is not as important as having one that people consistently follow.

Still didn’t understand a thing

Thanks <3

RIP league of legends game.

I thought you said "Memory safety ++"

Useful for implementing callbacks, when you want separate compilation. qsort is an example. Though std::sort is faster for any particular type, it has to be instantiated for each type it is used for leading to more generated code. With void*, we can avoid that.

... The entire point of wanting tabs instead of spaces is because people have different preferences. 2 Spaces sounds extremely annoying When having to count indent levels :/

just learned the name of the registers can change based on your system. So for 32bit its EAX, EBX etc.

There’s nothing wrong with leaving school with a little knowledge on a lot of topics. It gives you far greater flexibility when entering the job market and once you get a job, you begin to specialize in what it is you do every day. The reality is sometimes you don’t know what you don’t know, knowing a little bit about a lot helps you understand what there still is to learn and how that’s connected to other topics/technologies.

And is it possible to work part time writing code? I’m just looking for a part time job