I already told you to never show me this again. Fuck beta?

It's using the same technique that they used on the early consoles. It's a really nasty hack and if you were running that kind of workload, you'd damn well better know the particulars of why it sucked then and is now completely ridiculous. We've had 64bit options available for decades and it's truly sad that a workload of that size would be forced to run under paging hacks to access that much RAM.

Not this one?
Pentium 4 at 4.0 GHz
I see some old news articles about it being canceled, but I remember the hype for it.

There isn't enough information there.
That's a single core, 4GHz Pentium 4.
Did they give it a proper refurb before running that test, or are they using the original thermal grease and a clogged fan and heatsink?
Because I highly doubt that test machine (the ONE sample of that CPU) was actually in WORKING condition, given that the 3.8GHz model doubles the score.
That's not even getting into the higher multimedia instruction sets that the i7s have which newer Passmark probably bangs on.
Plus, we saw this happen. The Core line of CPUs was ridiculous in comparison to the previous Pentium 4. Not 'Core i7', but 'Intel Core Solo' and 'Intel Core Duo'.
They made the Pentium 4 look like a serious lemon.

I still find unending amusement in the fact that we "know" so much based on observing distance objects. It doesn't take a scientist to see how much data is lost optically, just walk from one end of a large room to the other.

I must say, I see something like 'portable to other compilers but gcc', and it gets me thinking.
What are those guys smoking? The systemd guys. The GNOME guys.
If I'm a GNOME on Linux user, I'm essentially being forced to migrate to a new operating system to keep using GNOME.
systemd doesn't support other libcs. systemd requires gcc extensions.
Linux, a fine OS kernel which is supported by a wide variety of userland options, and it looks like we're trying to homogenize everything to a degree which is frankly the opposite of what makes Linux itself an amazing piece of work. Things are becoming inextricably linked to components they previously may have INTERACTED with but did not RELY on. The alternatives are being pushed aside by the very depth and breadth with which these newer projects are gobbling up system responsibility.
These issues lie at such a basic level that it's poisoning the entire ecosystem.

There's a problem with this idea of intuitive. "using or based on what one feels to be true even without conscious reasoning; instinctive."
I'm curious about how a computer is supposed to be intuitive.
Let's take a journey into the past for a moment and look at historical computing machines, what they were used for, why they were built. I'll take as an example the artillery computer on a warship from the great war that brought the technology upon us. Differential Analyzers were mechanical devices which performed calculators. When it came to the use of these devices in ship-board artillery, the interface was simplified to assorted knobs and gauges where the operator dialed in the appropriate parameters to get the necessary result. However, the action being performed - the calculation of trajectory using mathematics - was in no way simpler or more intuitive, it was buried under an appropriate interface that hid the details necessary for performing the task at hand. This had the result of making it so an artillery man no longer needed to concern himself with the deeper understanding of the task he was performing.
I fear we've run head-long into this case where we expect our tools to do the work for us rather than allowing us to work more efficiently.
I'm seeing 'simplified' interfaces slapped onto complex machines that end up overlooking the details. I'm seeing this idea that the tool needs to to the job, that the user need not understand how the job is done. That is not a good thing.
Computers don't have the potential to change the world, they already have. Unfortunately, as a direct result of how deeply they've changed the world, we no longer feel it necessary to actually learn what we're doing.
We just want the computer to do it for us.

On every platform, this idea has led to horrible design decisions. We have things like Metro and Unity which have decided that a never-ending list of every installed application is better for a new user - when it outright requires that user to know what they're doing to get any work done. We have this issue where people are so afraid of complexity that we're oversimplifying things to the point of breaking them.
But the inescapable truth is that we live in a complex world, and do complex actions. Many of those actions cannot be simplified to the degree that "end user" is going to be able to effectively do them, because the entire idea that "end user without a working knowledge" should be able to do complex tasks is pure fallacy.
Computers aren't getting simpler because we're streamlining the user interfaces, the tasks users must accomplish aren't getting simpler because we're streamlining the user interfaces. We're screwing everyone by trying to simplify a complex world beyond reason.
As it stands, KDE might be the gold standard of desktop environments, and I feel that's because they haven't been afraid of the inherent complexity involved in the system. If they manage to appropriately refactor the user experience while not crippling the environment, they might be on to something.
Chances are, we're about to lose the value of KDE, much like we lost the value of so many other projects over the years.

They've been struggling with that one for an awful long time. Even to this day, using the OptiFine mod can give a huge performance increase on many machines just because it's doing things a little smarter with it.

Maybe only the Nazis are better off.
Nuclear disarmament starts at home. It's an abject failure.

X.org people themselves admit Wayland is better because those X.org people are Wayland developers.. That's not an unbiased source by any means. It's also a source that one would expect knows what they're doing to some degree, but that's always debatable.
Personally, I have a major trust issue with Wayland. Also with SystemD. I feel my reasons are very sound, they include the fact that both of these projects have been rabidly pushed since their project inceptions. The trust issue is that I've been told these are the next big new great thing since there wasn't a line of code written. I've been told that they solve all of my problems while providing none of the solutions.
I've been computing most of my life and these projects have some serious delusions of grandeur that have frankly made me want to keep them off of my systems at all costs. Don't break the system because you think you're doing it better, do it better first.

That would be an example of retroactive continuity.
The standards people being MAD because their SI prefixes were being used 'incorrectly'.
But the fact remains, bits and bytes were never metric units to begin with.

Linus has been a user of these tools for decades now. He's one of a select few who have the capability, experience, and understanding necessary to even approach the depth of the bug that they're talking about. He's one of the few who have been heavily relying on them for his entire technology career.
What I'm saying is that Linus knows his tools. He knows when his tools are need in of repair. He knows what to expect from them and by this point should have a solid understanding of their quirks.
Sometimes tools don't work how they're supposed to.
I'm inclined to believe the master woodworker when he tells me his blade is dull and needs to be sharpened.
I'm inclined to believe the master programmer when he tells me the new version of his compiler is generating incorrect code.
I'm probably a below average programmer myself, but I've hit enough depth to understand some of the context of this issue. I read through a bit and see them doing the footwork necessary to deal with the issue. That's something I don't see people doing when they're blowing smoke and being bitchy.
Linus has a bit of an attitude problem. But so does almost everyone else in a position like his, where he is the project leader for something incredibly complex. Like the local event equipment guy who can be a real ass when he's in action, but knows exactly what he is doing, how to do it, why he does it how he does it, how to explain it to his workers, and gets it done on schedule, because he's been doing it for a very long time and lives and breathes the job.

This is all beside the point, which is that you could only write your post because I previously slept with your mother.

I don't understand it anymore. How are we not beyond the need to replace random letters with asterix? I mean honestly, the summary goes on to comment about it. It's a waste of space. Just fucking say it already.

I really wish my iPod Touch would just accept the fact that I've disabled wireless instead of nagging me to turn it on every time to decides to send a packet back to the NSA. It's seriously frustrating to try to work offline on devices that don't want you to.