Talk:Array length: Difference between revisions
The best insight into languages comes from tasks which are external to them
No edit summary |
(The best insight into languages comes from tasks which are external to them) |
||
Line 20:
: And it's also possible that different JS implementations will optimize ternary expression handling. But mostly I don't care about optimizations which yield less than a factor-of-2 improvement - with exceptions to the rule, of course, being in the context of resource-critical bottlenecks. Reason being that quite often there's factor of 1000 (or better) optimizations available if you instead take some time to digest the relevant issues. (And the reason for that is that efficiency is not a universal good, but something which relates to a specific effort.) --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 17:21, 8 October 2015 (UTC)
::Absolutely – which is why it seems a pity to be starting up more of these simple documentation-lookup entries – missing the chance to actually formulate a problem and task (external to the inner concerns of particular models of computation). A task focus does does yield much more insight and relevance (as well as better coverage across languages).[[User:Hout|Hout]] ([[User talk:Hout|talk]]) 17:38, 8 October 2015 (UTC)
| |||