branja

I agree. Yet I want as much inference as possible as you described upthread

Look into success typing

People have in fact talked about these things. Including the science being great, the psychology being preposterous yet entertaining, and the disco being disco.

https://arstechnica.com/science/2014/11/stuck-on-mars-with-n...

insects also reproduce to account for death, requiring food sources, which there are none of on Mars

Okay, thanks. I appreciate the counterpoint. I guess I'd like to see it both ways: bots limited to human speed and bots not.

For the same reason the APM are limited: to ensure that what we are doing is really focusing on advancing strategy rather than brute mechanical skill. If I played against an AI using nothing but the rendered frames and sound of a game as input, I might not even make the stipulation on reflexes. I'd be humbled if I lost.

As it stands now, most of the games I like have bad AI. Sure, it can be fun to play a hack and slash against lots of little, dumb minions, but FPS, RTS AI these days still don't cut it as savvy opponents. Often they have inhuman perception, direct knowledge of game state, or higher starting resources, but they make abysmal decisions.

Yes, I realize these are unlikely, expensive goals and incremental progress is how things are done. I just want to know if it's possible or desirable to emulate actual human reaction time.

Do you disagree this would in principle help separate strategy from godlike reflexes?

to emulate human handicaps at the interface layer. I didn't say it would be free

ideally they'd train it on real keypresses rather than actions

I work as lead dev on a 5 year old web app I took over from a previous dev and his team of subcontractors about a year ago. It's very helpful to see into the past when there's no way to just ask the previous dev.

Try interactive rebase. https://robots.thoughtbot.com/git-interactive-rebase-squash-...

This is much easier when I actually need to trawl through history to find things.

You can do both. Squash your working branch to a single commit, then rebase. That way you still get a clean view of just the changes introduced in the branch, and don't have to resolve merge conflicts every step of the rebase.

Not animations, but git-scm.com is excellent

The Native Americans of the Appalachians used to burn the brush down in the forests and otherwise cultivate the land, yes.

If you fell into 100C hot and extremely acidic water it would be a big problem – Barbara Cavalazzi, University of Bologna

all the fun problems in CS are intractible