28 ms·
I'm actually going to call bullshit on the entire notion of a "critical 3%". That may previously have been true, but so, so many apps these days have the majori
by kllrnohj 12y ago
I'm actually going to call bullshit on the entire notion of a "critical 3%". That may previously have been true, but so, so many apps these days have the majority of their code on critical paths, and time and time again I've seen apps that are generally sluggish just because of death by a thousand cuts. There wasn't a 3% focus area where fix it and everything is magic, it was a "well, this anti-pattern permeates your entire app, and now you have to significantly overhaul 50% of it to fix it"
The modern era of low-latency interaction with high framerate scrolling & animations has completely changed the performance landscape. Performance is not something you can bolt on at the end anymore.
- aristus 12y agoThe idea of the book is to take all advice with a grain of salt, and measure yourself. Inefficiency spread everywhere is kind of a best case. Or it might be an indication that you are looking at the wrong layer of the stack. Also, judging from your jargon I'd say you work in games. Games are an entirely different dimension from the mainstream of programming.
- kllrnohj 12y ago> Inefficiency spread everywhere is kind of a best case. Not if that inefficiency is enough to cause visible issues, which is not unusual. > Also, judging from your jargon I'd say you work in games. Nope, I work on mobile apps. Which are not entirely unlike games.