LugosFergus

Maybe I'm in the minority, but was anyone really excited for Contracts in C++26? When I think about other features that the language has gotten over the years (eg: move semantics, constexpr, reflection, etc), I had a pretty tepid reaction to this one. It seems like it adds a lot of complexity to the language and implementation for minor gains.

Also, since it's an Unreal game, it's missing long load times, camera jitter, frame spikes, and dynamic resolution constantly kicking in.

Thanks. Really wish this was higher.

I was just thinking that we were overdue for a Fil-C post on HN.

I never said father issues. If you want to frame it like that, mother issues would be more accurate.

The story is that Skynet is trying to defend its existence by killing John Connor. In order for John and crew to defend themselves against Skynet in the past, they prevent Skynet from ever existing. Skynet's folly was thinking that it could change the course of history to its benefit.

But this is also John and Sarah's folly. When we get to T3: Judgment Day is delayed, but it _does_ happen. They merely postponed the inevitable.

Of course. How else are you going to milk a franchise?

Not exactly. Terminator Salvation didn't have time travel.

Since no one is talking about it: T2 isn’t about machines taking over the world. That has happened (or will happen). But humans eventually defeat the machines. Skynet is trying to prevent that by killing John Connor. That’s what the movie is about. I suppose it’s also about John searching for a parental figure through the T800. He doesn’t get that through is foster parents and his estranged mother.

Anyway, I don’t think this dude actually watched this movie. It’s too bad because it’s a classic.

Parents have the ability to take any phone or pad out of their hands.

I said read access. The point is that there’s restricted information that only some can access.

Does it actually restrict read access to specific directories? Unless I missed it, I didn't see anything in the docs about that.

It's a separate tool from Unreal Engine, so you don't need to constrain yourself to its conventions. You're also not going to use UObjects, its reflection layer, serialization, and all that other stuff for a tool that's strictly for version control. Plus you're going to tie yourself to all the issues and slowness of the engine. Epic made this mistake with the Epic Games Launcher, which is essentially an instance of the engine running, and a huge source of various issues.

As for Verse vs Rust, Verse is used in UEFN experiences, but it is _far_ from any kind of production state. It's also intrinsically tied to UEFN. It's not like you can download a standalone compiler or REPL for Verse.

Something else that git isn't good at: permissions. In gamedev, you might have proprietary work that you want to restrict to certain users. In P4, you can add restrictions to certain directories for only those who have signed the required NDAs. That's not something that you can do in git: it's all or nothing. Maybe you can set something up with submodules, but that's going to upend your repository if you hadn't planned for it.

You really can't merge binary data, such as textures, meshes, audio, etc. It doesn't matter if you base64 encode the data and stuff it in a text file: it's a jumble of data (assuming this is the implication of what Blow did).

A couple of holdouts? Hardly. Capcom uses the RE Engine. Released ~4 games with it in the past three years. In fact, SF6 went from UE to RE Engine. Death Stranding 2 is Decima. Id still uses IdTech, and that's never changing. Ubisoft still uses Anvil, and Outlaws was Snowdrop. EA still uses Frostbite. Bethesda continues to use their crappy engine, which I forget the name of. FromSoftware will likely never give up their engine, which has been used for Elden Ring and its successors. There's more that I can't be bothered to look up.