Pavel Valakh | Lands of Koastalia 🐏

"Some applications need performance" - Literally the first thing you said in this video is wrong. "It will have a profound effect on the structure and readability of your code, generally a negative one" - Again, I could say the exact same thing about clean code and OOP. - Readability and reasonable performance are not mutually exclusive. - You don’t need to write in assembly to outperform most apps today. - But you do need to reason about data structures and their memory layout, something that becomes impossible when everything is split into a million tiny classes doing their own thing. When you say that most applications aren’t sensitive to microseconds, you’re missing an important point: - It’s not about a single component doing its job in microseconds, it’s about the entire system working together. - There’s a name for this, "death by a thousand cuts". - You might think the cost of small inefficiencies is negligible, but your system ends up slow because every object is "thinking for itself". "Most of us live in a world where our programs execute in human time." - That’s for sure, and it’s painfully obvious when using modern software. - Everything is slow enough to be noticed by the human eye. - In fact, I could almost draw the frames on paper in real time, it’s that slow. "Our machines are so fast today." - Yes, but "our programs are even slower" by a huge margin. Regarding the last part of your video, where you sneaked in a reference to Casey Muratori’s video without properly mentioning it: - It’s honestly sad how disingenuous you are about this entire discussion, even after Casey put enormous time and effort into engaging with you on GitHub. And one more thing that’s often overlooked: - Good performance is a first order effect. - But it can also be a gateway to second order effects, like new features or entirely different design decisions. teapawt.net/vkrajacic/status/19178…