All this app needs to do is display 200 characters of locally stored text. How can this operation possibly fail at the loading stage. Why do people program like this.
I often wonder, what exactly is it doing in that time? A three second stall is enough time for ten billion CPU operations. What are they being used for? What ten billion calculations are happening between my right click and the context window displaying?
literally nothing on windows happens instantly. you right click? wait a few seconds. open file explorer? feels like it’s downloading the html from a server on the moon. the notification center? yeah go get a coffee first before it loads in the one (1) notification
Also from our #GDC19 tech postmortem: the transition into Fisk Tower in #SpiderManPS4's intro mission. The interior space is much larger than the exterior envelope, and too big to hold in memory at the same time as Manhattan. So we use some careful camerawork to hide the swap!
Please don't do this.
Provincetown has one of the highest vaccination rates in the country.
As vaccination rates increase the percentage of cases that are in vaccinated people NECESSARILY increases.
Visual Studio stalls for over two minutes whenever I accidentally clicked the "class view" tab, so I used ProcMon to find out what it was doing.
It is doing a linear search over a 730GB file.
Multiple times.
Amazing.
omg games do not need neural networks for any of this. You can do it with a straightforward rules database, procedural triggers, and a writer who knows how to operate Excel. I did a whole talk on it eleven years ago.
I liked this video so much, I decided to write up all the bugs in it. Maybe other devs can spot things I missed, or speculate likely causes and assignees.
(I've omitted repro steps for 280-character brevity.)