Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I also observe this bias, I imagine it is an artifact of > versus >= on the pixel boundary.


It's because the left pixel is checked before the right pixel (the settling behaviour section). This is common in games where you handle movement input (left, right arrow keys) - if you press both of them you'll always go one way, because that way is checked first for movement.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: