bbllee

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.

Reminds me of 'What Intelligence Tests Miss: The Psychology of Rational Thought,' the most interesting cognitive science book I've read. http://www.amazon.com/What-Intelligence-Tests-Miss-Psycholog...

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.

    // 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.

For complete clarity, see also the lines

https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core...

The score is (arbitrary reference constant) / (geometric mean of runtime). Bad performance ==> longer runtime ==> lower scores.

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.

Looks like http://nubisa.com/ is interested in native (read: mobile, desktop) app development in JS.

Looking at the linked benchmark file appears to bear out this claim:

https://github.com/Nubisa/jxdocs/blob/master/benchmarks/core...

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...

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.

Sorry, this relates to the posted link how?

This one is so much smaller it takes a lot more effort to make it seem threatening.

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?

The article focuses on the potential harm to one or more prominent families' reputations; as you deduce, this kind of evidence would not only harm reputations but may also complicate land ownership.

A dead commenter said, "Any startup ideas on cleaning the Ocean? I guess no country wants to pay for this yet?" and I had two thoughts in response:

There's a reason for the word "tragedy" in the phrase, "the tragedy of the commons"; "cleaning" probably isn't going to cut it; ocean warming and acidification will quite possibly cause mass extinctions.

Yeah, hard bounce off the atmosphere trades angular momentum for radial velocity and increases eccentricity, meaning next time you hit the atmosphere is gonna be even worse.

And its orientation.

Yes, it is "just" lots of math-- IF you know what the atmospheric conditions will be like. Having worked with a few atmospheric density models, I have the distinct impression that they are meant to give a mean density estimate but that variations are significant and velocity variations are not even modeled.

I think the parent of your comment meant: "the speed optimization is important if we want to have UIs as complex as an IDE _built with these new APIs_" --because polyfills do lots of work to emulate browser features.

Yes, you are missing something. :) This is trying to provide polyfills for and build on top of Shadow DOM and Custom Elements.

While some of the features in them could be provided just by templating stuff (though it would be mildly to very inconvenient), at least the visible DOM / shadow DOM separation and scoped styles wouldn't be possible.