bonkmaykr: extra bonks @bonkmaykr@gameliberty.club

@xianc78 At that point you might as well ditch the degree and save money to get your company off the ground.

Be honest: college is a scam especially in cases like computer science where they make you waste money and time on superfluous classes, and the only worthwhile thing you get out of it is maybe you'll get hired somewhere

@grizzlywhisker

@graf Oh look, an evil company shitting on another evil company for a publicity stunt to brainwash customers!

BD-R* You can't write a ROM, shit.

I'm going to start buying stacks of 4K BD-ROMs to move my old gaming clips and blender projects and stuff to. I can't keep taking care of more and more 8TB hard drives that are going to die someday and having to hoard and replace them.

The price-to-capacity ratio is worse, sure you can get an 8TB WD Blue for 130 dollars now, but those are mechanical and electronic, they get old and die. SSDs, they get old and die and those are twice as expensive. I'm on low income.

Discs only rot and even then they take way longer. I'll be able to procrastinate on revising that old stuff for as long as I am alive.

While I'm deciding what to move to those discs it will also be a good opportunity to finally delete years of stuff I just don't want anymore. The data hoarding is only half because I'm overprotective but also because that shit piles up and gets hard to sift through.

Okay so I've tried about a million different things and everything either just A. goes super speed, B. Freezes after Tick #2 or C. Behaves exactly the same

I am 100% certain this should be working because it is exactly what I did with the FPS cap...

Somehow my timings are wrong...?
It's gotta be some kind of typo in my delta timer, I've checked everything else.

It is a good thing I have not started writing enemy AI yet or else the whole thing would have to be rebalanced.

I have been doing some research on the inline keyword in C++, since my IDE (CLion) is... giving it a lot of preferential treatment.

From what I have read, correct me if I am wrong, it is primarily an optimization **when used on functions**. Forcing the compiler to insert the function contents directly wherever it's called when it assembles into opcode, removing the overhead of calling a subroutine, but potentially decreasing efficiency in other ways--low level CPU cache/branch predict stuff the compiler will probably decide for me anyway and that I don't have a great understanding of yet.

However, I cannot find a super clear answer on what cons this may have for *variables*.

Say I have a static variable in a namespace:

namespace stuff {
uint8_t x = 69;
}

What are some potential DRAWBACKS, if any, to making this inline? I can only find information on advantages, but that it should otherwise be left alone because the compiler will do it anyway if it's analysis deems necessary. The consensus seems to be "none" but I want to be sure because there is a lot of bad advice out there.

Thanks

@PurpCat I am interested 👀