3 ms·
That's nice in the abstract, but in real life, shitty performance costs people money and sanity right now, and that cost scales up with the number of users. Al
by TeMPOraL 6y ago
That's nice in the abstract, but in real life, shitty performance costs people money and sanity right now, and that cost scales up with the number of users.
Also, arguably, auto-saving existed in 90s - and the primary reasons it wasn't as nice as it was today were UX (wasn't enabled by default IIRC) and hardware (spinning rust wasn't good enough to support transparent auto-saving every other second).
- lmm 6y ago> That's nice in the abstract, but in real life, shitty performance costs people money and sanity right now, and that cost scales up with the number of users. So do crashes, and so especially does silently outputting the wrong answer. Slow but reliable beats fast but flaky every time, and it's much easier to speed up a working program than fix a flaky one.