Sounds like a good idea to dump flash. Like you need a good reason.
See also DesignedOnaLan.
Should we merge this sorta-ShallowPage into DesignedOnaLan? Page size almost suggests we do so, but the name of this page is catchy (and DesignedOnaLan isn't; I'd love to find a better name for it). Just wond'rin'.
Not all short pages are shallow. Quotables that will actually be quoted are cool. Of course, I had no idea either page existed, so it's questionable whether either page should remain as they are. Try to find a patternish name and combine the two of them, such as RespondQuickly?. (*) We could then talk about the 150ms reaction time barrier for interactive systems as well. -- SunirShah
GratificationTime??
ResponseTime??
RespondNow?. {Expedite,Rush,Hasten}Response?
Well, you can never respond now by logical exclusion (i.e. now is the action, the response is a reaction)
I deleted the previous crumby discussion about pattern name templates in the hopes this would be better. Imperative-object is not a good one for this. Although we're talking about a process (-->verb), we're talking about the quality of that process (-->adverb), so verb-adverb would be better, or adverb-verb which are almost grammatically equivalent. Essentially, imperative-qualifier. So, RespondQuickly?, ReactQuickly?, ReactFast?, LoadFast?, etc.
If I were to end this discussion in the next minute, I would pick RespondQuickly?. (There's a rule about second guessing oneself.) -- SunirShah