Some people using the site now were probably not even born when "DLL hell" was still something that was actually a problem, rather than just a term that Slashdotters parroted.
I know that's the argument that Swedish prosecutors are using, but it's rather a stretch to claim that they require Assange to incriminate himself in order to charge him.
I think it's safe to assume that the article is talking about reference encoders.
Why would that be safe to assume? That is a useless comparison, and not one that would interest the BBC in the slightest.
What is far more safe to assume is that it is a comparison between their current h.264 encoding setup vs. whatever h.265 coded they would use in practice. Neither would be the reference codec.
Everybody do most definitely not know that PNaCl is the way to go. PNaCl suffers from many difficult problems, such as being based on LLVM bitcode, which is not static, but is machine-specific and has undefined behaviour. The PNaCl team has put a huge amount of effort into working around those fundamental problems, with quite a bit of success, but it's still not in any way a very good solution.
wasm will take advantage of some of that work, it seems, but its bytecode will be more strictly defined and designed for the purpose, which will help a lot. wasm is much more based on asm.js, being at first just a binary encoding of it. That in itself is a huge improvement on the hacky way it was originally implemented, though.
Slashdot Mirror
It doesn't have an ad blocker, it has an ad replacer.
That's quite a different thing.
Actually, it's probably a lot less.
That was the definition of a kilogram for a few years, several centuries ago. You're a little bit out of date.
This was the definition for a few years in the eighteenth century, before it was quickly changed.
It's such a bad definition, it was not worthy using even back then.
Some people using the site now were probably not even born when "DLL hell" was still something that was actually a problem, rather than just a term that Slashdotters parroted.
I don't believe that apple will want swift to grow outside of the apple walled garden.
Yes, this is why they are porting it to Linux. Because they don't want people using it on Linux. This makes perfect sense.
They also have automatic migration tools to fix these things for you. In practice, it is not a problem.
Guard forces you to exit the function in the else branch, and "guard let" introduces a symbol in the containing scope rather than the contained scope.
Yes, that horrible, horrible Apple. How dare they make their code BETTER!
Oh, so you're an Android user, then.
No, I don't. You lied about me, what is that supposed to prove?
I know that's the argument that Swedish prosecutors are using, but it's rather a stretch to claim that they require Assange to incriminate himself in order to charge him.
True. This is why nobody claims this.
No, until he's raped someone he is not a rapist. "Rapist" is not a legal term. It is a word that means "a person who rapes".
I think it's safe to assume that the article is talking about reference encoders.
Why would that be safe to assume? That is a useless comparison, and not one that would interest the BBC in the slightest.
What is far more safe to assume is that it is a comparison between their current h.264 encoding setup vs. whatever h.265 coded they would use in practice. Neither would be the reference codec.
Your president is ridiculously powerful compared to those of most other western democracies.
Samsung have no control over telco update deployment.
Bullshit. They can make sure the telcos are contractually obligated to publish timely updates.
They don't, because they don't give a shit.
Surely, "thought" is a long way short of being sufficient to extradite someone ?
You are aware that this is a newspaper article, and not the actual extradition request?
You are confusing h.264 and h.265. Nothing you said makes any sense.
Not really. Both are similar in terms of efficiency.
The advantage h.264/h.265 have is dedicated hardware, not efficiency.
That would also fall under the category of "100% lie".
Except it doesn't. That's 100% a lie.
What it does include is mobbing up to bully people into killing themselves.
Or do you also think that is also totally important protected free speech?
She did a pretty shit job of that, didn't she? Reddit is pretty much exactly as full of vile, disgusting shit as it always was.
This will actually make asm.js code more readable than it is right now.
Everybody do most definitely not know that PNaCl is the way to go. PNaCl suffers from many difficult problems, such as being based on LLVM bitcode, which is not static, but is machine-specific and has undefined behaviour. The PNaCl team has put a huge amount of effort into working around those fundamental problems, with quite a bit of success, but it's still not in any way a very good solution.
wasm will take advantage of some of that work, it seems, but its bytecode will be more strictly defined and designed for the purpose, which will help a lot. wasm is much more based on asm.js, being at first just a binary encoding of it. That in itself is a huge improvement on the hacky way it was originally implemented, though.
In other words, it's exactly like Java
Point A: Unlike Java.
Point B: Depends on your definitions, but fairly unlike Java.
Point C: Unlike Java.
Point D: Unlike Java.
Point E: Unlike Java.
How you can be given five different ways that wasm is unlike Java and conclude that it is "exactly like Java" is not easily comprehended.