Similar principle but O(log(n)) istead of Stalin sorts O(n).

I wish. Sadly the google play store requires monotonically increasing build numbers, so any option of resetting build numbers after major releases goes out the window.

Bringing more modern tools and features to existing large code bases is “destroying his reputation”? Bjarne and the committee is constantly extending and modernizing a language with code bases older than me. Yes that means the old stuff has to be kept around but that is the price of allowing existing code to migrate gracefully instead of just throwing it out of the window. There is a problem with some missing rails to enforce current and saver techniques but Bjarne is not denying that.

That is the mindset that gives us text editors using 100% cpu to blink a cursor because their css triggers a bug in the web browser they ship to render the text editor.

You can be memory save without shipping a whole browser, but disregarding power and memory efficiency will just make performance gained by hardware evaporate in overhead.

“But throughout that time, I actually had no inkling what game development was actually like. How hard the designers, programmers, artists, producers, and everyone else worked,” he says. “The struggle to bring a vision to life with constantly shifting resources. The stress.”

Then tell us about it. Make it heard where you get Stressed and where you rub up on the state of the art. List off what had to be finished in crunch time. What got pushed by Marketing or Management. Leaving everything up to a nebulous “you don’t know” makes any criticism easily dismissed and reduces leverage against systemic issues.

how do you stop it on client side? I’m not sure if it has been deployed into the wild but these days computer vision is good enough to just work off the images. Capture image signal, fake usb mouse outputting movements calculated from image data. If this isn’t already available it’s only held back by the need for extra hardware.