The idea of lamenting climate change by having nostalgia for the days when piling into a car and driving across the countryside would guarantee a handful of smashed insects on the windscreen is funny to me.
This absolutely infuriates me to the point where I'm struggling to remain civil. My blood instantly began boiling after reading that sentence.
Why the @#$% does some web designer think it's a good idea to disable mousewheel scrolling?! What does this accomplish? What feature do you gain? What was the goal?
I just can't for the life of me grok what would be going through someone's brain when they decide "Hey, you know what would make this page better? Disabling scrolling with your mouse wheel!"
EDIT: Maybe the intent was to do something else, like implementing smooth scrolling in JavaScript, and it's not working properly. But if that's the case, the answer is that web devs need to stop trying to mess with scrolling. Implementations rarely work correctly in every browser and it just ruins the UX. Just stop messing with scrolling!
In this case it's a bug, as I'm not trying to 'disable' the mouse, but track scrolling and then make the menu 'stick' to the header when the user scrolls down the page. A common design pattern which increases usability quite a bit.
It hits a nerve when a programmer or designer either tries to fix something that isn't broken and ends up making it even worse (Such as web pages that try to implement smooth scrolling), or removes functionality for the sake of simplicity and it lowers usability. Yeah, in this case it was a bug, but let's not pretend it doesn't happen deliberately sometimes.
Whether it hits a nerve or not, there are more productive ways to express that you don't agree with an implementation. You acted like a bully and that's completely unacceptable.
I think part of is the nature of it. Why would you get sufficiently into this scene, care enough about this one game to post video after video of you speedrunning it, to then cheat? The challenge for someone doing it manually is to do it manually; the challenge for someone doing it TAS is to do it TAS. Without the challenge there is literally no reason to do it. So while lack of evidence can't really prove anything, there really isn't that much motivation to cheat. If it was a complete nobody claiming they had manually set a record, yeah, that's suspicious, but someone well involved in the scene either is playing the long con for something that they themselves don't care about (and which they can't really revel in since any sort of in person interaction would show they're frauds), which is unlikely, or they're legit.
>Without the challenge there is literally no reason to do it.
What about money? Fame? Aren't these reasons?
And there are countless examples from history of 'the best' in whatever area getting caught at cheating just to stay 'the best'. I'm not really sure what you're getting at with this.
Actually plenty of people who have been deep in the community have cheated. It happens. But given that this run was performed live during a stream where he is reacting to chat it is pretty unlikely that he was doing playbacks of the entire stream.
People use them as another tool for finding glitches and exploring the possibility space of the game's systems. They're basically using debugging tools and in some cases even looking at memory allocations etc.
As for full length tool assisted runs, I just find them to be a fascinating new lens to examine these games under. It's cool (depending on who you ask...) to see what the game looks like when another computer program is piloting it perfectly towards the goal of 'finish as fast as possible'
I poked around a little and it seemed like the majority of it is related to analytics events (googleanalytics/autotrack)
I suppose the author just wants to know a little about how their blog and writing is performing in the wild
Sort of off topic, but it would be interesting if the browser handled these common cases instead and gave the user a way to opt-in/out. I suppose it sort of does by broadcasting those events to the js listeners in the first place.
