Instead of guessing you could just use the exact same config and mods and see if you get a similar result.

To be bottlenecked by the GPU in TF2 you'd have to replace it with an Etch A Sketch.
Single channel RAM, possibly lower clocked/worse timings too and the updates that happened since 10 months ago certainly don't help.
Also different config and

It's from 2011. Do you really believe it's 240 Hz? Do you really believe that it was so many years ahead of everyone else's technology?
It's for a Playstation, which does not output anything over 60 Hz.
It uses HDMI, which didn't support 240 Hz until HDMI 2.0 in 2013.

So do the math. Do you really think it's 240 Hz?

You mean like the "don't use GeForce GPUs in datacenters" in the TOS?
Or the "1/2 per customer/household" retailers are already using?

Well let's take a guess if it'll be effective.
Magic 8-Ball says: "Abso-fucking-lutely not."

Somebody is going to donate 2000$ with the message "#freeXQC". Calling it now.

Seriously though the whole thing is laughable.
Tell someone straight to go suck a fat cock = completely ok, happens 3000 times a day in Overwatch.
Tell someone gay to go suck a fat cock and then realize that's not even an insult = ban pls
If you ban someone for using "gay" as an insult then you have to do it regardless of the targets sexual orientation. This is the reverse of "black people can't be racist". It's either always an insult or never, you can't just pretend it's fine as long as there are no minorities involved and then act like it's suddenly EVIL.

Also Dallas Fuel "banning" him instantly for the match on the same day without telling him because he was benched anyway. That's some PR move.

Well about the image: You can probably read where it says "13-Stage Integer Pipeline" and "10-Stage NEON Pipeline"?
And all the complicated looking stuff beneath that?
For comparision purposes the A7/A53 pipeline:

https://cdn.arstechnica.net/2011/10/20/arma7-a7pipeline-4ea040a-intro.png

I think you get the idea now.

About the rest:
-branch prediction also automatically means speculative execution (unless you built some really weird shit).
-correct
-yes, same reason for out of order, actual cause is the speculation depth.
-yes. OoO exists mostly to allow for deeper speculation so any OoO core should be affected while inO can be shallow enough to be safe, but doesn't have to be. ARM11, A7 and A53 are safe for that reason.
-yes, so do OoO CPUs.

I'm not sure how much you know about CPUs but I guess I'll make a post explaining how Spectre and Meltdown work and for that I need to explain how CPUs work on a basic level (grossly simplified wherever possible) anyway.

#38
Not my circus, not my monkeys.
Meltdown is fixed and the patches should already be applied if you update regularly.
Spectre patches are difficult, might not be completely safe, might lead to crashes or might simply cause massive performance issues. But you have to keep in mind that the code still needs to be executed and it needs to run while you're accessing the sensitive data. So if you're not letting some shady website run javascript (praise noscript) while you're doing your online banking then it's not really possible to exploit it unless your pc is already compromised.
JS is also getting patched.
So yes, malware and JS got a lot scarier but the same rules and precautions as before apply: Don't run untrusted programs, be careful with javascript and apply the security updates.
It's not like you were safe before if you just hoped nothing would happen.

#39
Yeah that's more or less completely wrong.
Despite what Intel claims Meltdown is not an unavoidable side effect of a feature, that's why only Intel and a handful of other CPUs are affected.
Spectre v1 is and that can't be fixed in hardware, but can easily be fixed in software.*
Spectre v2 isn't and can be fixed in hardware**, but can't be easily fixed in software.
They just mashed all 3 together.
Maybe if I'm bored I'll explain how it actually works.
Spoiler: It's not simple. The simplified explanation is still pretty complicated, otherwise it wouldn't have happened.

*The problem is guarding against a whole new class of similar-but-not-quite-the-same attacks.
**Already difficult to exploit on some hardware.

Ok just in case you still don't believe me:
https://developer.arm.com/products/processors/cortex-a/cortex-a8

https://developer.arm.com/support/security-update

Because its pipeline is this monstrosity:

http://processors.wiki.ti.com/images/0/09/Cortex-A8Pipeline.png

Source is me. I mean you could search for it but if you understand those then you understand why it's possible.

Read again.

5 is basically the minimum length for pipelining to work properly, the A53 got 8 stages. That does not qualify as long.
Assuming some standard 2-way superscalar you have the branch and the load issueing in the same cycle. Then load-to-use-latency an AND and then the load, but that just needs to make it into the LSU because it won't be canceled, only the writeback but no one cares about that.
So if you have some piece of shit like the IBM PPE with a 21-stage pipeline where branches even go into a different pipe that is delayed for 3 cycles you just need a fast enough L1 cache and early enough bypasses and then you can make bullshit happen.

Then there are things that are completely orthogonal to being in-order like runahead execution that give you a window just as long or even longer than out of order execution.
VLIW with load hoisting and intra cycle/bundle/whatever bypassing can also be happily in-order (and usually are) and still make it easy.

Of course there is a major difference in timing but that's basically irrelevant. Instead of forcing a miss to RAM and being able to take your sweet time the data already has to be in the L1 because you've only got a few cycles at best or need it to be cycle perfect at worst. But that doesn't matter because you can just run the code twice to pull the data into the L1 first and then access it.

Realistically though if you're using an in-order core it's some sort of embedded application or similar and you're only running your own code (you probably trust that) or it's some kind of big.LITTLE arrangement where another cluster is full of out-of-order cores and you need to apply the patches anyway.

And now we proudly present stage 2:
https://skyfallattack.com/
They're actually using James Bond movie names.

トベン トルキア
エメ エスティーダ クーレー デゥフーラ

#15

Too late, the memers have come to take you away. It was nice knowing you.

#16
Correct. If he was unsure whether or not he'd get 144 fps then maybe it would've mattered but he should've asked about that.

Apart from the budget preferred size and resolution would also be important.

Is that just a random statement or do you want me to slowly piece together the actual question or is it really that hard to ask "Which 144 Hz monitor would you recommend?" if you want a recommendation for a 144 Hz monitor?

How is that even related?
Would you have to buy a new monitor if you upgraded to a 1080 later?

Let's take a step back.
You're not choosing between multiple 27" 144 Hz monitors or multiple 24.5" 240 Hz monitors, you're choosing between a 27" 144 Hz and a 24.5" 240 Hz.
And apart from that the only information is the brand name.
And you're going to make a decision which one to buy based on what people think the quality of their products in general is like, not the actual quality or performance or features of the monitor you'll buy.
And you think that one of the brands got a bad reputation but now they are sponsoring more esports events and that somehow has made their products better?

I'll be honest I have no idea what you think quality is so I can't tell which of the monitor that you didn't name is of better "quality" by your definition.

Yes.

No idea, heat is always an issue with Coffee Lake when not delidded.

Maybe April, maybe later.