We all can't have great RNG 😂

Also programs in C, I'm in love.

Yeah the dude is awkwardly handsome, no homo. If only he wasn't such an Apple fanboy, he'd be marriage material.

@@blaynebradley3896 lmao why is this so real

​@@lapidationshe uses apple? Time to block him lol

"I think"!? 🙂

Same😢

I worked overnight on a production deployment. My feature update was error free, but updates and system it depended on were in intensive care most of the night. We wrapped up around 2 PM Saturday, so my day was destroyed.

Although I have no clue about his stuff but yes. It reloads the DLL that the main game is using

I am not jdh, but here's an advice I can give. Just read code, and write code. Stop reading books, or even documentations (to some extent). Reading books only gives the *illusion* that you understand something, because the author actually explains the concepts to you, so your brain pretends that you understand. But often times, you don't. Reading code helps you understand the implementation and how it works, and more importantly writing code yourself makes sure you understand how the parts work.

Same here, I would love to know!

If you've done those already you're ready to just mess around and build stuff. Just pick any book in computer graphics with good user reviews online and you should be good to go. To get good tho you not only have to read the book but also write loads of code. As for reading code it's harder than it sounds and person a big weakness of mine but reading code is good advice.

Read and write tons of code.

And btw, what's in those DYNLIST macros?

gruvbox!

@@jdh Thank you.

@@jdh a few things that you should add are mipmapping, witch removes the moiré effect. An example of this would be in Minecraft, try disabling it and see what it looks like.

@@Inyourface3445 mipmapping isnt a few things, its a thing also if you watched ANY of his recent videos you should know he is for that software render style

Description

@@joaoruss0 thanks

There is no way of hiding weird stuff on plain sight in C I don't know what the hell are you talking about. C is the only language on earth that completely prevents you from doing that since every function call that happens is explicit and every function must have a unique name (no function overloading). If weird stuff happens in C then it happens right in front of your face every single time. Also UB doesn't appear out of thin air, UB happens because of invalid code or invalid inputs wich is absolutely not "thin air".

@@marcossidoruk8033 I can't argue with this. I clearly failed so say what I wanted to say. I guess you have to help me on this one lol, but what I wanted to express was that there's certain rules experienced C developers (I am not one of them, I just had opportunity to ask some questions to experienced C developers)follow to avoid shooting themselves in the foot, which might not be entirely obvious for people learning C for example. I'm sure UB was not the best word but there's always amazing problems you can run into C if you try hard enough or if you're naively using language features without an understanding of the standard or the hardware. Basically, the best C programmer I know is someone who has a very deep knowledge of the C standard and who's job is formal verification, when we asked them if they trust themselves to write C code they said no.

@@xhivo97 Well odin has the same problems, even in a language like Rust you will have the same problems when you try to implement a performant memory allocator and have to use the unsafe keyword everywhere. Until full program agnostic memory correctness formal verification exists that is just how programming works, no way around it, if what you have to do you can do fully in something like safe Rust then good for you, but that will not always be the case. Also it is worth to mention that not every program is safety constrained. A videogame for example you care that it doesn't crash often, but it need not be perfect, the software for a commercial airplane autopilot tho.... What I am really trying to say is that If your friend works at formal verification, then he is probably thinking about problems very different from videogames where safety is the absolute priority, so his answer may not be that illustrative for, lets say, gamedev.