On the combat side of things, Tiny Combat Arena is well reviewed: https://store.steampowered.com/app/1347550/Tiny_Combat_Arena...

A lot of people also seem to like VTOL VR: https://store.steampowered.com/app/667970/VTOL_VR/

On the combat side the top games are War Thunder (which I don't recommend due to it's microtransaction model), DCS World (flawed and expensive but still fun), IL-2 Battle of Stalingrad (good WW2 game) and Falcon BMS (excellent, but focused on the F-16 and has a small community)

“Flawed and expensive but still fun” is perhaps the best capsule summary of DCS I’ve ever seen.

That's useless in this case. You need to be able to prove that it will work with all inputs, and there are too many combinations of inputs to exhaustively enumerate.

That would be true of any software system we put into an airplane, yet we have deployed software into airplanes.

If your AI has linear / continuous output, testing it should be no different than any other software.

There is no way to determine that a non-trivial neural network won't drastically diverge in output due to small changes in input (eg one pixel attacks on image classifiers). This is true for all current models I know of.

Almost all neural network implementations have continuous outputs (ie the nodes in the output layer produce a value between 0 and 1). That doesn't change the above issue at all.

This is much less of an issue with traditional methods

Not quite. Lifetime annotations prevent you from accidentally using references after the value they refer to has been freed. They track how long things will live, instead of defining how long they will live.

Basically they turn use-after-free errors into compile errors.

(I'm using 'free' here to mean cleaned up in general. Lifetimes can track stack values.)

Why would static types require you to create additional classes?

Willing to die and willing to endure torture are different things. Everybody breaks given enough pain.

The top (selected) path is 23 hexes from start to finish, but the winding closer path is 24 hexes.

Not the issue here, look at the end of the selected path, where the cursor is. If you go down where the cursor is instead of right the path is 1 step shorter.

Oh you're right. My bad, sorry.

There is no line. If Google decides to ban you, your only recourse is to post online and hope your story gets enough traction for it to become a PR issue for them.

I've worked on several teams that required PRs before merging, and there was never any toxic behavior. Everybody was happy with it.

Nobody in this thread insulted you.

Telling someone that they are confused about what a web browser is looks pretty clearly like an insult to me.

Encrypting web traffic is a necessary step in making dragnet surveillance impossible.

I don't care if they 'dragnet survey' my users who are just looking for 20-year-old data sheets. Fact is, not everything needs unbreakable encryption, or a warning label for lacking it.