You can achieve no delay without using a zero delay. Graphic Control Extension blocks may be omitted between images and so multiple images can come in a row without anything defining a delay between them.
See the last instance of the phrase "graphic control" in the document to see that multiple images can come with no intervening GCE blocks and see the paragraph containing the 5th instance of that phrase to observe that a GCE block only affects the first image following the GCE.
The collision risk will depend very much on the altitude at which they are placed... this is also a big determiner of design life (N years before the orbit decays and they come back into the atmosphere) and might also have some effect on signal strength / geometry.
In short, rationality is not the same thing as intelligence and general intelligence does not correlate with rational behavior nearly as well as we might like it to. Individuals with high intelligence can and do put their mental endowments to work to argue for mistaken ideas and execute irrational plans.
I'm now thinking of an intelligent individual who made a small misstatement in conversation, then, when challenged on that point, proceeded to explain why he was not mistaken for several minutes... then finally wised up and admitted that his original statement was wrong.
Seems double-silly. First there's the whole "smaller is better... I mean, whoops!"-ness of the blogpost. Second is the general choice of benchmark: JXcore is supposed to be a multithreaded JS engine, so it seems like you'd want to benchmark its multithreaded performance against V8's single thread perf. on some workload that can take advantage of multiple threads.
It appears that the reported numbers for benchmark X are _the # of times that X can be run before one second elapses_, so parent comment is correct and the premise of the blogpost (that the new node.js version with V8 has worse performance than the earlier version / the private fork has better performance than the new version and slightly worse performance than the old) is contradicted by the evidence presented.
Not a good way to look competent, posting something like this. Countdown until edit or takedown...
Doesn't this line calculate the amount of time it takes to compute a single task? (elapsed time / number of runs = time per run) Doesn't this mean that JXcore is actually faster, since the number would be smaller with more runs?
// Suites of benchmarks consist of a name and the set of benchmarks in
// addition to the reference timing that the final score will be based
// on. This way, all scores are relative to a reference run and higher
// scores implies better performance.
I find one of your premises very thin: browser implementors are implementing DOM promises, so promises were clearly not invented solely to make up for the difficulties of Node.
Could a lawyer (preferably from NC) chime in about real estate law and if there's something like a "statute of limitations"? Would adverse possession (or something like it) in effect wipe away any crime committed in coming to possess a piece of land?
See the last instance of the phrase "graphic control" in the document to see that multiple images can come with no intervening GCE blocks and see the paragraph containing the 5th instance of that phrase to observe that a GCE block only affects the first image following the GCE.