12 results for "edea0997ee55500ef1f2224c57f6829e"
Amiga Workbench had multitasking in 1985.
>>107096663
That's even creepier. I get the heebie jeebies from this guy...
>>520476038
I find tiktok slop distasteful.
Gentoo is the only linux distro I consider any good. Other distros are just houses of cards held together by super glue. I use gentoo for my computing needs and there is nothing special about it, the meme "install gentoo" is stupid too I think installing gentoo is easy and simple. Gentoo literally just works while other distros break all the time.
Then tell me how I am succeeding by just chillin'? I do a few jobs and get paid, then I'm chillin' again until new opportunities arise, which is multiple times a year. Such a boring slide thread.
How do we convince Japan to like final fantasy again
But the fucking cattle does not understand. They will be like "so what schizo" and then when the digi ID comes they'll be screeching "why didn't we do anything before it was too late!?!?!"
>>106918897
1. I agree that goto obfuscates code execution paths, however I don't think recursion is "complex", so I'd allow recursion - Recursion can be extremely useful and sometimes it offers the most natural way to solve a certain problem.
2. I agree, infinite loops mean the program halts and cannot do anything unless the loop causes it to run out of memory / crash and that is not ideal either even if the program autorestarts itself
3. Not sure what initialization means here, I agree it could be avoided but sometimes you have to heap-allocate deep struct members individually if that's what it means
4. I agree functions should be kept as simple as possible, but no forceful splitting into multiple functions should be done however
5. Runtime assertions are great for debug builds, I assume their assertions are only present in debug builds.... I agree!
6. Unnecessary scope is always bad because it leads to increased complexity and dependencies, I agree.
7. I agree.
8. I agree, preprocessor should not be abused, that leads to obfuscation
9. I agree, I don't remember when I had to do multi-dereference, probably never - Function pointers are fucked because they can be null or point to invalid addresses, I agree they should be avoided. Faggots like to do "OOP" in C with function pointers, I don't see the point in that! You can't even get smart pointers in C because there is no destruction mechanism (function) for stack objects so I don't see point in OOP in C!
10 I agree, I always use Wall and address sanitizer and such tools in debug mode.
>>41300679
>If that were so, I've already retroactively ended that chaotic system
You put yourself in here, deliberately, faggot. We are one, you are I and I am you.
No heist no buy
I just cancelled game pass I refuse to pay $30 a month for Skyrim
Why doesn't steam have an android launcher yet