Anecdotal observation: A few years ago, I made a video game for an early 1960s computer, the PDP-1, running in an homegrown emulator in web technology. [1] Amazingly, the game runs at 60 frames per second (yes, you could do this with early 1960s tech), and, amazingly, browsers were able to render the emulation, including a rather complex simulation of the dual-phosphor screen, at 60 fps (you could do this in 2016). Admittedly, Chrome wasn't the fastest browser then, skipping a frame now and then, but caught up with others browsers over the next year. That is, until a few revisions ago, when something inside Chrome went terribly wrong, causing the browser to grind over the emulation in single-digits frame rates. Other browsers, like Firefox and Safari, are still running the emulation (which is as of 2012) happily at 60 fps, but these combine just about 15% of the intended desktop audiences. So for all measure and market concentration, the project is dead by now, due to a bug in the dominant browser. More importantly, it fails to deliver the proof it was intended to provide, namely that you could do a video game at 60 fps around 1960, because you randomly can't do so today.