I just wonder if Netflix with bother with H.265 for non-4K. Perhaps, as you say, it will make good sense for those without super-fast internet connections.
They delivered on the Gamecube and the Xbox 360 back when they were ATi, they delivered on the Xbox One and the PS4... I'm not seeing a reason to assume they're going to screw up the Scorpio, other than a pre-existing personal dislike of AMD.
As I posted here: Seems to me that TBL could have done a much better job phrasing the point that backdoors might be intended only for government use, but bad guys always find a way to use them to break security systems wide open.
What is the person on the street really going to make of "they may end up getting better at it than you are"?
That's not much of a counterpoint to a complaint about Roku's UI. The whole point of the Roku is to avoid using a full-blown high-power (in both senses of the term) device.
A very good point. None of this affects BitTorrent, which already has everything.
It might affect piracy in another way though: if the obfuscation can be broken, it might open the gates to 'hoarding' Netflix content then cancelling your subscription.
If you only worry about out of bounds errors and null pointers, sure.
Well, you get a valid C interpreter. That was the question.
There is another type of bugs: The "solution" didn't actually solve the problem.
Well of course it's not a useful thing to do in practice. If you want assurances that your C code isn't going to behave differently on different (but compliant) C platforms, you'd go with something like MISRA C, as you say.
I broadly agree with your other points.
I'm not sure I'd say C++ memory-management is 'manual' though. Reference-counting has its drawbacks, but it's hardly fair to say it's 'manual'. (And if you're using C++ and not using smart pointers, you're doing it wrong.)
Agree that the absence of dynamic typing is not a flaw, but a valid design decision.
Seems rather obvious: how hard it is will depend on how large the circular runway is. If it's somehow 100 miles across, the pilot wouldn't even notice the curve.
It won't affect Jihadists. That's for sure. They'll simply create new accounts, inform their fellows about it and continue to spread their bullshit.
Well, it probably would affect them, it just won't stop them completely. Whack-a-mole isn't ideal, but it's better than ignoring the problem. There's an analogy in computer security.
The much bigger effect will be on channels that offer controversial opinions.
Indeed, I see a real risk of misguided leftists ('SJWs') wanting YouTube to ban, say, Sam Harris, for saying mean things about Islam.
Oh, right. I think the probability of them removing instructions is close to nil.
I hope there's no modern games out there that use busy-loop timing
Agreed it's not likely. The Xbox One S had a slightly greater GPU clock-speed, so non-uniformity in the Xbox One platform isn't totally new.
I just wonder if Netflix with bother with H.265 for non-4K. Perhaps, as you say, it will make good sense for those without super-fast internet connections.
What? Why?
They delivered on the Gamecube and the Xbox 360 back when they were ATi, they delivered on the Xbox One and the PS4... I'm not seeing a reason to assume they're going to screw up the Scorpio, other than a pre-existing personal dislike of AMD.
with hardware H.265 support because I'm pretty sure Netflix is going to use that one day.
What use-case do you have in mind? 4K? How likely is it you'll want to watch Netflix on a 4K screen that doesn't have a Netflix app built-in?
If you're not thinking 4K, why care about H.265?
Even if it adds instructions, so what? A game targetting both platforms would need to be developed with both platforms in mind.
Not even close, no.
Anyway, 245W is pretty damn low by gaming machine standards.
What? The CPU and GPU are both by AMD, as with the original Xbox One.
I guess they only have to do better than the PS4 Pro.
Microsoft is paying attention to 1080p users, promising that all modes will be available to them.
Meaning what?
Also, 6.8GHz on the RAM? Goddamn.
Those stories aren't about war
Of course they are. Don't be silly.
they're about the depravity and inhumanity that can live inside all of us.
Yup. And war.
"Superior". Nice and impartial.
Ignoring, you know, the entire first-world outside the USA.
So many AC comments labouring the point that yes, TBL was in favour of 'EME'. Is it the same AC, I wonder?
As I posted here: Seems to me that TBL could have done a much better job phrasing the point that backdoors might be intended only for government use, but bad guys always find a way to use them to break security systems wide open.
What is the person on the street really going to make of "they may end up getting better at it than you are"?
He could have pointed to a physical-world analogy: the TSA 'master keys' that can open all sorts of luggage padlocks. For a while, only the government had them. Today, anyone with a 3D printer can make a working copy.
So I suppose Linux distros should stop distributing over BitTorrent if they don't want to be known for piracy?
That's not much of a counterpoint to a complaint about Roku's UI. The whole point of the Roku is to avoid using a full-blown high-power (in both senses of the term) device.
A very good point. None of this affects BitTorrent, which already has everything.
It might affect piracy in another way though: if the obfuscation can be broken, it might open the gates to 'hoarding' Netflix content then cancelling your subscription.
None of that means they aren't screwed.
If you only worry about out of bounds errors and null pointers, sure.
Well, you get a valid C interpreter. That was the question.
There is another type of bugs: The "solution" didn't actually solve the problem.
Well of course it's not a useful thing to do in practice. If you want assurances that your C code isn't going to behave differently on different (but compliant) C platforms, you'd go with something like MISRA C, as you say.
I broadly agree with your other points.
I'm not sure I'd say C++ memory-management is 'manual' though. Reference-counting has its drawbacks, but it's hardly fair to say it's 'manual'. (And if you're using C++ and not using smart pointers, you're doing it wrong.)
Agree that the absence of dynamic typing is not a flaw, but a valid design decision.
Then you get a valid C interpreter... obviously.
https://soylentnews.org
Seems rather obvious: how hard it is will depend on how large the circular runway is. If it's somehow 100 miles across, the pilot wouldn't even notice the curve.
...but in far lower volumes. Great job with the disingenuousness.
It won't affect Jihadists. That's for sure. They'll simply create new accounts, inform their fellows about it and continue to spread their bullshit.
Well, it probably would affect them, it just won't stop them completely. Whack-a-mole isn't ideal, but it's better than ignoring the problem. There's an analogy in computer security.
The much bigger effect will be on channels that offer controversial opinions.
Indeed, I see a real risk of misguided leftists ('SJWs') wanting YouTube to ban, say, Sam Harris, for saying mean things about Islam.
they attack us in hopes that we will make more restrictive laws
Well, not exactly. Getting crypto banned isn't the end-game of Islamic terrorism, but yes, it is more about the response than the body-count.
Schneier wrote an excellent piece on this topic: "What the Terrorists Want".