Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Submission + - WebAssembly and the Future of JavaScript->

Nerval's Lobster writes: WebAssembly is the next stage in the evolution of client-side scripting. In theory, it will improve on JavaScript’s speed. That’s not to say that JavaScript is a slowpoke: Incremental speed improvements have included the rollout of asm.js (an optimized subset) in 2013. But WebAssembly—while not a replacement for JavaScript—is intended as a “cure” for a variety of issues where JavaScript isn’t always a perfect fit, including video editing, encryption, peer-to-peer, and more. (Here’s a full list of the Web applications that WebAssembly could maybe improve.) If WebAssembly is not there to replace JavaScript but to complement it, the key to the integration rests with the DOM and Garbage Collected Objects such as JavaScript strings, functions (as callable closures), Typed Arrays and Typed objects. The bigger question is, will WebAssembly actually become something big, or is it ultimately doomed to suffer the fate of other hyped JavaScript-related platforms such as Dart (a Google-only venture), which attracted buzz ahead of a Minimum Viable Product release, only to quickly fade away afterward?
Link to Original Source

Submission + - Apparent Technical Glitch Halts Trading on New York Stock Exchange->

edeefelt writes: Trading in all symbols was temporarily halted on the New York Stock Exchange floor Wednesday due to an apparent technical issue.

"NYSE/NYSE MKT has temporarily suspended trading in all symbols. Additional information will follow as soon as possible," the NYSE said in a statement on its status page.

A technical issue caused the trading halt, Reuters reported, citing a source. Trading stopped around 11:30 a.m. ET.

The Nasdaq reported no technical issues and said it continues to trade NYSE-listed stocks.

Link to Original Source

Comment Re:Badly written and unpublished (Score 2) 304

Replying to myself.

The relevant stats are about years of healthy life, and not life expectancy. That didn't change at all.
So whatever effect there is has nothing to do with dying, and only with being sick (Huh?)
Years of healthy life has a lot to do with wording of questions, and just looking over the italy stats in the raw
data, the years of the anomaly are also the years in which the data table states that the question was worded differently.

So, my conclusion is: nothing to see here, move on.

Comment Badly written and unpublished (Score 3, Insightful) 304

This paper is in its infancy. It is somewhat garbled, the methods don't really specify the methods.
The methods are basically "we graphed mortality over time". But you can't really criticize it much,
because it is not published, and probably not submitted yet. The only question is why did it get to slashdot?

The most likely explanation for the effect at this stage is some kind of error. Either in the calculation,
or as the authors point out, in the wording of the questions (which probably would be a good idea to
test before this paper is published ?)
"Standardized translations of the questionnaire have been used; nevertheless it is likely that linguistic or cultural differences, as well as changes in the wording of questions, have influenced the way the respondents indicate a longstanding health problem or disability and their way of communicating the types of restrictions caused by this problem"
Or, in the population measured (migration from East-Block countries?) or many other possible problems.
All these I'd bet much higher chances than a real health effect.

Comment Re:won't help for Samsung note 2 (Score 1) 240

I don't think this is true for some devices. As the grandparent said (me), for the Samsung Note 2, charging current depends strongly on the USB cable used - same charger will charge at different rates depending on the cable. (And sometimes the same cable + charger will charge at different rate depending on luck).

Comment Re:won't help for Samsung note 2 (Score 1) 240

I don't think it has to do with voltage drop. A cable usually will not show a voltage drop ~0 resistance for 2m of cable. And, same cable will charge other devices without any problem. A cable might burn out with too much current. Maybe that's the worry? I haven't really heard of that happening....
Even the originally supplied cable is rejected sometimes. And, if you get a bad charging rate, just unplug and replug the cable for another roll of the dice.
No, I think it is a simple bug in the charging control in the phone.

Using TSO is like kicking a dead whale down the beach. -- S.C. Johnson

Working...