Compilation method isn't what's going on here. Static type systems are, as explained in the article.
Whatever consciousness is, it's not obviously required for an AI to start manipulating its surroundings to its advantage, which is one if the fears here.
I'd willingly pay that price if it delivers on what they said in the marketing. But it appears we'll have to wait.
Many people live in places where summer and winter are different, and they happen at the period of a year.
I call it silly too. While also admiring many of its ideals.
The argument suggested in the article is that harvesting plants also kills insects.
There are enough differences to warrant using different abstractions when appropriate. RAM never fails. Or, it never fails in a way that application code is expected to handle. RAM is cached, and cache is so fast that…
There is a cause I believe in pationately, but somehow not everyone sees it the way I do. Do you think it's ok for me to use hyperbole, if I'm sufficiently convinced I'm defending the right viewpoint?
It's simple. "Bytecode" is just a kind if encoding. The only thing it does is make programs marginally smaller and marginally quicker to decode. It's not enough to justify enormous switching costs. Let's talk about what…
Or they could just target WebGL and asm.js, which already works in Chrome, and let's see how long Google sits around with Chrome being slower at a popular use case.
Compilation method isn't what's going on here. Static type systems are, as explained in the article.
Whatever consciousness is, it's not obviously required for an AI to start manipulating its surroundings to its advantage, which is one if the fears here.
I'd willingly pay that price if it delivers on what they said in the marketing. But it appears we'll have to wait.
Many people live in places where summer and winter are different, and they happen at the period of a year.
I call it silly too. While also admiring many of its ideals.
The argument suggested in the article is that harvesting plants also kills insects.
There are enough differences to warrant using different abstractions when appropriate. RAM never fails. Or, it never fails in a way that application code is expected to handle. RAM is cached, and cache is so fast that…
There is a cause I believe in pationately, but somehow not everyone sees it the way I do. Do you think it's ok for me to use hyperbole, if I'm sufficiently convinced I'm defending the right viewpoint?
It's simple. "Bytecode" is just a kind if encoding. The only thing it does is make programs marginally smaller and marginally quicker to decode. It's not enough to justify enormous switching costs. Let's talk about what…
Or they could just target WebGL and asm.js, which already works in Chrome, and let's see how long Google sits around with Chrome being slower at a popular use case.