Both games have gameplay loops that were ahead of their time. Relatively free exploration + combat + RNG "loot" constrained by needing to return to town to heal/restock.
The point of a rewrite is to safely delete most of that arcane knowledge required to operate the old system, by reducing the operational complexity of it.
And sometimes it can't even handle it then. I was recently porting ruby web code to python. Agents were simultaneously surprisingly good (converting ActiveRecord to sqlalchemy ORM) and shockingly, incapably bad.
For example, ruby uses blocks a lot. Ruby blocks are curious little thingies because they are arguably just syntax sugar for a HOF, but man it's great syntax sugar. Python then has "yield" which is simultaneously the same keyword ruby uses for blocks, but works fundamentally differently (instead of just a HOF, it's for generating an iterator/generator) and while there are some decorators that can use yield's ability to "pause" execution in the function to send control flow back out of the function for a moment (@contextmanager) which feels _even more_ like ruby blocks, it's a rather limited trick and requires the decorator to adapt the Generator to a context manager and there's just no good way to generalize that.
Somehow this is the perfect storm to make LLMs completely incapable of converting ruby code that uses blocks for more than the basic iteration used in the stdlib. It will try to port to python code that is either nonsensical, or uses yield incorrectly and doesn't actually work (and in a way that type checkers can even spot). And furthermore, even if you can technically whack it with a hammer until it works with yield, it's often not at all the way to do it. Ruby devs use blocks not-uncommonly while python devs are not really going to be using yield often at all, perhaps outside of @contextmanager. So the right move is usually to just restructure control flow to not need to use blocks/HOFs (or double down and explicitly pass in a function). (Rubyists will cringe at this, and rightly so... Ruby is often extraordinarily expressive).
The fact that such a simple language feature trips them up so completely is pretty odd to me. I guess maybe their training data doesn't include a lot of ruby-to-python conversions. Maybe that's indicative of something, but I digress.
> This is fake Iranian propaganda. It makes no logical sense. The force sent to extract the F15 officer (approx 2 C130s of people) is far to small to retrieve tons of nuclear material stored at Isfahan.
And how does it make any logical sense to send 100+ spec ops guys in two big planes to rescue one (1) guy in a remote mountainous location? That's begging for >1 casualties and PoWs in situation which would otherwise be capped at 1. Mickey mouse nonsense.
It's far more logical that there was a different operation planned, one that would actually require hundreds of special ops guys, like securing a strategic site. And just because two planes were "stuck in the mud" doesn't mean there weren't more involved or planned to be.
> And how does it make any logical sense to send 100+ spec ops guys in two big planes to rescue one (1) guy in a remote mountainous location?
I’m a former Air Force officer, and can attest that this is in fact a long-term standing policy. “Never leave a man behind” exists because if we didn’t have that policy, pilots would be too risk averse to fly the missions aggressively.
Check out the “Notable Missions” section for a few very public examples over the past decades:
I never claimed there was no CSAR operation, and you still can't explain why you need 100+ spec ops guys in two big landing planes for this particular operation.
The US military had information assymmetry and aerial dominance. They established contact with the missing WSO through a magical CIA technology known as a "satellite phone". They secured the area with aerial surveillance and strikes, then sent in a couple helicopters to do the extraction. Nowhere does this require 100s of operators on the ground, risking their lives and escalating to a ground war. This isn't the 1960s in Vietnam.
It's one of the reasons the US military is so good. As a soldier, you know they will come for you, behind enemy lines, so you can fight like hell, knowing that your fellows have your back.
> And how does it make any logical sense to send 100+ spec ops guys in two big planes to rescue one (1) guy in a remote mountainous location? That's begging for >1 casualties and PoWs in situation which would otherwise be capped at 1. Mickey mouse nonsense.
Fucking software engineer "logic." They're not playing starcraft, pushing around mindless units that will thoughtlessly follow any stupid order you give them?
I'm a person. You make it clear you'll abandon me the moment it's "logical," I will abandon you. If you make it clear you'll go the extra mile for me, I may be motivated to do the same for you.
No, I would absolutely not want 100s of guys blindly crawling over the dirt, I would want someone to pick up my satellite phone calls and send a couple helicopters.
At most there were a couple thousand casualties from violent riots that involved armed gangs (or sleeper cells if you want to go that route).
There were not "60,000" peaceful protestors executed by the government, as Trump claimed yesterday without evidence. That is murderous propaganda, blood libel intended to deflect from the actual mass murder of civilians by American forces e.g. the Minab school.
It was a narrative specifically designed to induce comments like yours.
reply