That’s only proof that it will never be enough to stop all cheating. But if the metric is if it reduces cheating then that proves nothing. Not saying I have proof that it does reduce cheating but I would personally bet on it reducing it somewhat at least.

It only works in so far that it makes making cheats harder to create and easier to detect. But it will never fully eliminate or catch all cheats.

Sure. But that doesn’t mean Secure Boot didn’t make it harder to create a cheat or limit what kind of cheat they could create this quickly. The cheat was a wall hack one and that is one of the hardest to stop AFAIK.

Some of it the hate probably amplified by cheaters and cheat makers. Though to be fair anyone can be annoyed at having to go into their BIOS and change settings…

I mean there is arguments against creating test for everything but that definitely isn’t a good one…

I wasn’t trying to say you can’t do remote development what I was trying to say was it’s not a good way for the whole industry. That and pointing out drawbacks of full remote.

The fact that you have such strict separation between programmers and designers leads me to believe your company hires a lot of people they don’t need to do jobs in a poor manner. I have very little respect for people who ‘design’ but can’t create.

This is the weirdest take I’ve read in a while… Thinking designers doesn’t create anything is just so wrong… And I’m not just talking about creating designs but also creating prototypes using components and e.g. unreal blueprints… Let’s not forget about taking the time to properly tweak values and all that…

I’m not going to share what games I’ve worked on as I like to have at least a faint divide between my online persona and real life one.

As a gameplay programmer I fully disagree. Just the ability to quickly ask a designer near you for clarifications or to if modifying the design slightly to save on time is worth soo much.

Asking over slack just isn’t the same as it adds more friction, takes longer, and makes it easier for misunderstandings to sneak in.

To be fair though it can be worth sometimes working from home to give you less distractions if you need some full focus time… And other jobs in the industry does gain a lot more from being fully remote…

Memory leak

Destructor

Dynamic dispatch

Execute

Not really. Unsafe doesn’t allow you to sidestep the borrow checker in a decent way. And even if you do it the Rust compiler assumes non aliasing and breaking that will give you loads of unexpected problems that you wouldn’t get in a language that assumes aliasing…

Testing something that only has side effects to the local scope is probably not too hard but that isn’t the most common case for gameplay code in my experience…

Going through another language basically has the same issues as unsafe except it’s worse in most ways as you’d need to keep up to date bindings all the time plus just the general hassle of doing it for something that could have been a 10 min prototype with most other setups…

Now sure it’s possible that I would have better result after doing even more rust, especially with some feedback from someone who really knows it but that doesn’t really change anything in just general advice to people who is already working on something in C++ as they likely won’t have that kind of support either.

I’m a gameplay programmer who have worked with Unity and Unreal and I’ve experiment with Rust for gamedev(though only for hobby projects) and for regular code. My conclusions so far is that Rust sucks for gameplay code, for most other things it’s kinda nice.

The biggest reason is that it’s much harder to write prototype code to test out an idea to see if it’s feasible and feels/looks good enough. I don’t want to be forced to fully plan out my code and deal with borrowing issues before I even have an idea of if this is a good path or not.

I would say though that because you are using ECS stuff it is at least plausible to do in Rust but at least for my coding/development style it still isn’t a good fit.