> "All of the things that work, however, are damaged by how lukewarm and _slow_ the overall experience is." Oh pssht, humans can't notice a response time of le

> "All of the things that work, however, are damaged by how lukewarm and _slow_ the overall experience is." Oh pssht, humans can't notice a response time of less than 2 seconds. Plus performance doesn't matter at all because you can add it later if you need it, which you don't. Anyway, you can't say it's slow until you've measured it and you can't complain until you have a fix. Besides, it's more important that the code is readable because it will be read much more often than it will be written. And furthermore, if you re-run the same thing a few times to warm the JIT up, discount startup time, ignore input and output time and network lag because they are external to the system and only measure the core function runtime, you'll find it's ackshually really fast (if you buy new hardware which is ifine because +$2000 computer spend is cheaper than developer time). And does a few seconds really matter, what were you going to do with that 10 seconds of response time, read a book or something? Slow? What do you mean "slow", launch time, hover response, switching response, time to finish redrawing a page? There's many things happening and you can't complain unless you narrow down exactly which specific sub-millisecond behaviour is taking too long for you - none of them? thought not. Stop questioning the dogma, hush.