Comments by "Zer0" (@ForeverZer0) on "Wookash Podcast" channel.

OOP is a great paradigm for humans to conceptualize ideas, but is bad for how machine code actually executes. I started with Ruby and then C# (both strong OOP) when they were each the "hot" language of the era, and it wasn't until I moved onto to C and other systems-level languages that I realized OOP is not the ideal way to program. It was a great for me from a learning perspective, but it took time to break myself of OOP practices when learning other languages.
21
@ I wonder how C and the plethora of other languages have survived and thrived so long without these critical access modifiers... I know the first thing I do when there is a function I want not in the public API/headers is dump the symbol table of the binary and search the private headers for it. C has plenty of legacy problems, lack of access modifiers is not one of them, those are just handy for API design, not functionality.
3
@quangtube I don't discount the usefulness of OOP languages, I still occasionally use them to this day. This was merely a commentary on the difficulty of breaking the "bad habits" that OOP leads to when it is all that you know. I have a feeling that it would be easier long-term to learn these paradigms the other way around, even though I think OOP is far easier to grasp as a total beginner.
2
@ There is hundreds of languages with a variety of different paradigms that are not OPP or C. If you don't want to use OPP, it doesn't mean that your only alternative is C, there are hundreds of languages that would fill that need.
2
@alexvitkov I never learned DX12 beyond the basics, so forgive my ignorance of it, but how does it even work to have a pointer to GPU memory? Whatever you write to it would need mapped to CPU space and transmitted over the bus no? From my understanding, you don't actually have a pointer to the GPU memory, it is simply the API's abstraction on how to use it, meaning they both have the same level of abstraction, DX12 just does it in a more intuitive and less-verbose way using a primitive pointer everyone understands.
2