A) It' s a w3c standarized effort
Close, but still wrong
We’re pretty early into the overall process—there is no draft spec or even final formal standards body chosen, just a W3C Community Group
But it will be an open standard, thats sure.
"The Cloud" needs this. Microsoft for example has used asm.js inside their office online product.
[T]he API surface area is that of the Web platform (e.g., WebGL for graphics) and thus WebAssembly use cases will contribute to driving forward the whole Web platform.
The inventor of javascript, Brendan Eich, writes in his blog entry covering WebAssembly about the polyfill plans:
It’s crucial that wasm and asm[.js] stay equivalent for a decent interval, to support polyfilling of wasm support via JS. This remains crucial even as JS and asm.js evolve to sprout shared memory threads and SIMD support.
He further writes:
Yes, we are aiming to develop the Web’s polyglot-programming-language object-file format. [...] wasm should relieve JS from having to serve two masters [FAQ entry here].
Most likely due to Mozilla's envolvement, WebAssembly even tries to address the "binary" barrier built up when dealing with WebAssembly on a client.
Javascript is a scripting language. It has weak typing. In order to be sure of *anything*, you *have* to test. I agree, using jquery is as stupid as using boost. But you still have to test your application, and best you do it automated. That's what these frameworks are for.
Either we do it, or we let nature do it. And we do it right now. All this "world hunger" problem isn't just more than population control. Or think about the program China's been pulling off.
admittedly, this is also true for all feedback.
The difference is, it gets saved in the cloud, and your data can be sold to third parties.
Ship that by default if you dare!
Yes, exactly.
The recent release of firefox 38.0.5 on june 2 has been below the radar of many news sites, including Slashdot, because it was only a "patch" release.
However, 38.0.5 included real feature changes, meaning the inclusion of a proprietary web service. I not just hate that firefox added a proprietary web service prominently to its browser, also they smuggled this in in a patch release, avoiding press attention.
Firefox isn't a randy bitch dog that every dog inside the SV startup neighbourhood springs on, its a major web browser which respects its users. At least it was until 38.0.5.
I accepted that they added the social API, I understood their EME changes, I've thought firefox hello was a good addition. But for 38.0.5 pocket integration, I'm heavily disappointed by mozilla.
What would be your proposed copyright ruleset, so that content producers still can live off their creations?
And comatose patients who have been pronounced brain dead but whose bodies are unimpaired could wake up and walk again if they received a functioning new head.
Rather not. Its a body transplant, not a head transplant. Yes, the bodie's immune system will (or will not) attack the head, not the head's system the bodie's, but the head has the brain, and that's where most of the thinking is.
I guess in some years we'll figure out how to transplant heads, and perhaps one day we will have the possibility to grow brainless clones that have a computer controlling all the low level functions, to grow into an age they can recieve their new head. I guess this will rule out lots of ageing illnesses, but will open up serious ethical questions.
fortune: cpu time/usefulness ratio too high -- core dumped.
